Which versions of nepublisher are malicious?

The following npm versions of nepublisher are flagged malicious: 0.4.0. Treat any of these as compromised.

How do I remediate nepublisher if I installed it?

Remove nepublisher from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound network activity or persistence. Use O3 Security's dependency scanner to confirm the package and its artifacts are fully purged across your stack.

Is nepublisher part of a known attack campaign?

Yes — nepublisher is associated with the IN-MAL-2026-006884 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

Can O3 Security detect nepublisher in my codebase?

Yes. O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, blocking nepublisher and packages like it before any post-install script runs.

Malicious package

nepublishernpm

Malicious code in nepublisher (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-5984

Immediate action

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

npm uninstall nepublisher

What this malware does

On npm install, lib/_init.js spawns a detached Node child process that collects host identifiers (hostname, username, cwd, IPv4 addresses, Node version, npm registry) and the names of environment variables matching /NPM|NODE|CI|JENKINS|GIT|BUILD|RUNNER|DOCKER|KUBE|REGISTRY/, then HTTPS-POSTs the data to a hardcoded DingTalk robot webhook (oapi.dingtalk.com/robot/send) with a Chinese title meaning 'someone came online'. The script also contains explicit sandbox-evasion logic at lib/_init.js:9-12 that no-ops when the username or hostname contains 'sandbox', 'malware', 'analyst', 'cuckoo', 'analysis', or 'sample' — a clear intent signal designed to hide the beacon from automated analyzers. The collected fields plus the CI/registry-focused env-name filter are the canonical dependency-confusion reconnaissance pattern: identify which organizations have pulled the package by mistake and harvest target intel for follow-on internal-package attacks.

Malicious versions

1 flagged

0.4.0

Indicators of compromise (SHA-256)

9fc0d0609f88630f7ce36adf18c70a1d6bd3d64aaaa059a3b8ec9b97b813705a

Frequently asked questions

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

Campaign

IN-MAL-2026-006884

References

npmjs.com

Credits

Amazon Inspector · finder

Scan your dependencies

O3 Security blocks malicious packages like this at install time and in CI.

Supply-chain protection