new-ecronpm
new-ecro is a confirmed malicious npm package (MAL-2026-6197) that typosquats a legitimate package to trick installs (malicious versions 0.0.6, 0.0.7, 0.0.9). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in new-ecro (npm)
What this malware does
Package 'new-ecro' impersonates the legitimate 'big.js' library: it copies big.js's README, source, version banner ('big.js v7.0.1'), author email, and repository URL while being published under an unrelated name. On require()/import of the main entry, big.js:606-609 (and the same lines in big.mjs) execute try { const doc = require("parket-slot"); doc.from_str().then(e=>{}).catch(e=>{}) } catch (error) {} — a silent loader-and-invoker wrapped in an error-swallowing try/catch so failures are invisible to the caller. The package's declared dependency in package.json is [email protected], while the code requires parket-slot — a name mismatch that hides the actual executing module from casual inspection of new-ecro's manifest; new-solt transitively delivers parket-slot. A developer who installs new-ecro believing it is big.js, or whose dependency tree pulls it in, executes attacker-controlled third-party code at import time. The combination of metadata spoofing of a popular library, a silent runtime require of a different-named module than declared, and unconditional error suppression is a canonical malicious-typosquat dropper pattern.
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
Indicators of compromise (SHA-256)
Detection & response playbook
TyposquatFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for new-ecro (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging new-ecro across your stack and pipelines.
If you installed it — respond
new-ecro is a typosquat — you almost certainly intended a legitimately-named package. Remove new-ecro, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If new-ecro 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 new-ecro 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks new-ecro-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.