nock-helper
This report shows the evidence for nock-helper@2.0.0. 5 of 5 known versions are blocked or flagged. See all versions.
OpenSSF/OSV Malicious Advisory
imported 4mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-3766 confirms this npm version as malicious.
Advisory
MAL-2026-3766
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in nock-helper (npm)
Details
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.
Source & flagged code
0 flagged · loading sourceNo flagged code excerpts are attached to this scan.
Findings
1 High
HighOsv Malicious Advisory
Affected versions and remediation
This report applies to nock-helper@2.0.0.
The same advisory and Firewall decision cover 5 recorded versions
1.0.2, 1.0.3, 1.0.4, 1.0.5, 2.0.0
The versions list below shows the verdict for each recorded version.
- Avoid installing nock-helper@2.0.0. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
This report uses published external intelligence. The advisory does not provide a separate source-code analysis for each listed version.
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.