Malicious code in @magda/semantic-indexer-sdk (npm)

-= 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 consistent with a normal SDK client bundle.

Source: ghsa-malware (0ce59c9b39eeea0aa22df5f00b970f2543dc5da3003c0e73618cb45830d68274)

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.