Which versions of content-publisher-sdks are malicious?

The following npm versions of content-publisher-sdks are flagged malicious: 1.0.1, 1.0.2. Treat any of these as compromised.

How do I remediate content-publisher-sdks if I installed it?

content-publisher-sdks is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed content-publisher-sdks — how do I know if it already compromised me?

If content-publisher-sdks was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is content-publisher-sdks part of a known attack campaign?

Yes — content-publisher-sdks is associated with the IN-MAL-2026-014841, GHSA-cmjx-pgm3-j5gc, IN-MAL-2026-019771 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find content-publisher-sdks across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for content-publisher-sdks (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging content-publisher-sdks across your stack and pipelines.

Malicious package

content-publisher-sdksnpm

content-publisher-sdks is a confirmed malicious npm package (MAL-2026-12356) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.1, 1.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in content-publisher-sdks (npm)

MAL-2026-12356

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall content-publisher-sdks

What this malware does

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.

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.

Malicious versions

2 flagged

1.0.11.0.2

Indicators of compromise (SHA-256)

c3faac0139a1c2fd25d8b955e9290380bec365a1d3034fb793dfa723cb930463

39394cd04a494a4f6dceff2f54848e93a56bbbab2663fe9b48611ea39df58808

1a7ee39106f48b5051e4c75d6443dfe115d8926af9a6c8a4e96b8e01a2bcbb20

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for content-publisher-sdks (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging content-publisher-sdks across your stack and pipelines.
If you installed it — respond
content-publisher-sdks is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If content-publisher-sdks was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks content-publisher-sdks before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. content-publisher-sdks on npm has been identified as a malicious package (versions 1.0.1, 1.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014841GHSA-cmjx-pgm3-j5gcIN-MAL-2026-019771

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks content-publisher-sdks-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database