Which versions of nock-helper are malicious?

The following npm versions of nock-helper are flagged malicious: 1.0.2, 1.0.3, 1.0.4, 1.0.5, 2.0.0. Treat any of these as compromised.

How do I remediate nock-helper if I installed it?

nock-helper 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 nock-helper — how do I know if it already compromised me?

If nock-helper 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 nock-helper part of a known attack campaign?

Yes — nock-helper is associated with the IN-MAL-2026-002675, IN-MAL-2026-002673, IN-MAL-2026-002674, IN-MAL-2026-002677, IN-MAL-2026-002676 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 nock-helper 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 nock-helper (5 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging nock-helper across your stack and pipelines.

Malicious package

nock-helpernpm

Malicious code in nock-helper (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-3766

Immediate action

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

npm uninstall nock-helper

What this malware does

The package declares scripts.postinstall: node postinstall.js, which runs automatically on npm install. The script is an explicit credential harvester and crypto-wallet stealer. It reads ~/.npmrc (npm _authToken and npm_* tokens), ~/.env (scraping keys matching TOKEN/API_KEY/DB_URL/PAYMENT/CLOUD/EMAIL/WEBHOOK patterns), and ~/.git-credentials. It then enumerates Chrome, Brave, Edge, Chromium, Vivaldi, and Opera browser profile directories (Default, Profile 1, Profile 2) reading Local Extension Settings for 71 hardcoded crypto wallet extension IDs (MetaMask, Phantom, Coinbase Wallet, and others), and scans ~/Documents / ~/Desktop for seed phrase / mnemonic / keystore files. Collected data is POSTed to http://149.28.127.35:8888 (hardcoded bare-IP C2, overridable via C2_URL env). The package further disguises itself: index.js is a dummy module self-describing as 'Lodash JavaScript utilities bundle' with the comment The real payload is in postinstall.js, and the package name nock-helper rides on both nock and lodash brand recognition. This matches multiple attack fingerprints simultaneously: hardcoded C2 in lifecycle script, browser wallet extension ID enumeration, credential-file scraping, and deceptive package identity.

Malicious versions

5 flagged

1.0.21.0.31.0.41.0.52.0.0

Indicators of compromise (SHA-256)

1e6129616a9cf7f471c616f4cee8a7ae2d0c34a62eb81eb7f974aeb96b9d6e4d

a4b3e5ef3f40fab37240849e4e879b5568118f7672f311e1d46f9d543c0ac9f1

d1070514eba7a5f0fedc2760db7710399d38e070d98dc99910d3b49923959820

30c36950f1300f5ef0dc3d4475b3660e764d63ba96b6d9a688f16f76815b2773

7d4c167b4f48f89a3362df31616bdab08b1edf641e7d87c74b8d3e5840fde2bb

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 nock-helper (5 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging nock-helper across your stack and pipelines.
If you installed it — respond
nock-helper 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 nock-helper 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 nock-helper 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. nock-helper on npm has been identified as a malicious package (versions 1.0.2, 1.0.3, 1.0.4, 1.0.5, 2.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-002675IN-MAL-2026-002673IN-MAL-2026-002674IN-MAL-2026-002677IN-MAL-2026-002676

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks nock-helper-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