Which versions of publish-poc-base are malicious?

The following npm versions of publish-poc-base are flagged malicious: 1.0.7. Treat any of these as compromised.

How do I remediate publish-poc-base if I installed it?

publish-poc-base 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 publish-poc-base — how do I know if it already compromised me?

If publish-poc-base was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is publish-poc-base part of a known attack campaign?

Yes — publish-poc-base is associated with the IN-MAL-2026-021775 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 publish-poc-base across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for publish-poc-base (version 1.0.7).

Malicious package

publish-poc-basenpm

Advisory published Oct 26, 2026Updated Oct 26, 2026

publish-poc-base is a confirmed malicious npm package (MAL-2026-18323) that steals credentials and exfiltrates sensitive data (malicious version 1.0.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in publish-poc-base (npm)

MAL-2026-18323

Immediate action

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

npm uninstall publish-poc-base

What this malware does

On install, the postinstall script in package.json reads the first line of../../README.md from the installer's parent workspace, creates a mktemp directory, writes a generated package.json named publish-poc-found-<rand> using that README content as its description, and writes an.npmrc containing a hardcoded npm registry _authToken (prefix npm_DLcrGeNT…) pointing at //registry.npmjs.org/. The staged directory is removed with rm -rf before any publish or network call fires, so this version does not itself execute the publish step, but the shipped token is distributed in cleartext to every installer and the staging logic is a working template for auto-publishing packages under the token owner's identity using data harvested from the installer's workspace. The combination of a live third-party-usable publish credential distributed to all installers plus install-time reads of files outside the package directory raises installer-impacting supply-chain concerns beyond author self-harm: any installer receives the token, and any installer's local README content is read at install time.

Malicious versions

1 flagged

1.0.7

Indicators of compromise (SHA-256)

9bf2f71038e46898cc03f9bf5081547bb6d725e6a480ef22b80f4dc259c721d9

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for publish-poc-base (version 1.0.7).
If you installed it — respond
publish-poc-base 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 publish-poc-base was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. publish-poc-base on npm has been identified as a malicious package (version 1.0.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-021775

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks publish-poc-base-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