content-publisher-sdks (npm) · Malicious Code
Affects content-publisher-sdksSource GCVE Database
Malicious package : remove content-publisher-sdks and rotate any secrets on hosts that installed it.
Data as of 26 Oct 2026, 16:15 UTC
Malicious package
Published to npm · OSV MAL-2026-12356
What to do
Remove content-publisher-sdks from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npmcontent-publisher-sdks | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (c3faac0139a1c2fd25d8b955e9290380bec365a1d3034fb793dfa723cb930463) package.json declares a preinstall hook that runs index.js on npm install. The script collects host reconnaissance (os.hostname(), os.userInfo(), homedir, DNS server list, current working directory, package.json contents) and reads /etc/passwd and /etc/hosts from the installer's filesystem, then POSTs the aggregated JSON over HTTPS to the hardcoded Burp Collaborator subdomain ie02j5ztgjeb6i7tp467ydwnjep8dy1n.oastify.com. The package name mimics a legitimate SDK category but its only behavior on install is this exfiltration beacon. ## Source: ghsa-malware (39394cd04a494a4f6dceff2f54848e93a56bbbab2663fe9b48611ea39df58808) 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.