Malicious code in @magda/semantic-indexer-sdk (npm)
What to do
Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
npm @magda/semantic-indexer-sdk
- Affected
- every version
- Fixed in
- no fixed version recorded
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record MAL-2025-47009 lists affected ranges: npm @magda/semantic-indexer-sdk >=0
VerifiedObserved Structured OSV record; not marked as GitHub-reviewed.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- not scored
- EPSS
- No dated EPSS signal available.
Source description
As published by the source; long descriptions are shortened.
--- _-= Per source details. Do not edit below this line.=-_
Source: amazon-inspector (020b70c247fbc09223610616ef9c39ce27218404bff50de29b8a28706679fc14) @magda/semantic-indexer-sdk ships a minified `dist/index.js` bundle for a Magda semantic-indexer SDK. Static keyword patterns fired on the co-occurrence of `POST` HTTP verbs at several offsets in the minified bundle and on the substring `dyndns` at line 44075. These are keyword matches on a large rolled-up bundle — the `POST` occurrences reflect ordinary HTTP client usage expected from an SDK, and a `dyndns` substring in a minified blob does not by itself indicate a dynamic-DNS C2 destination (it commonly appears inside dependency names, TLD lists, or unrelated string tables). No hardcoded attacker-controlled domain or IP bound to install-time or import-time network I/O, no credential or environment scraping, no lifecycle-script execution, no dropper, and no obfuscated destination decoding are present. The observed patterns are…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from osv record MAL-2025-47009
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: GHSA-r2gq-mhfx-9mh3 Advisory: Malicious code in @magda/semantic-indexer-sdk (npm) IDs: GHSA-r2gq-mhfx-9mh3 Record: https://patchnext.com/advisories/mal-2025-47009 (revision 1, source checked 30 Oct 2026, 06:05 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Unrated Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed. ## Affected components - npm @magda/semantic-indexer-sdk: affected every version ## Suggested inspection (read-only) - `npm ls @magda/semantic-indexer-sdk --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`. ## Supported action No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on @magda/semantic-indexer-sdk. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/MAL-2025-47009 (OSV record MAL-2025-47009 lists affected ranges: npm @magda/semantic-indexer-sdk >=0) Commands are suggestions: review each one before running it.
Loading voting…