Which versions of ts-wross are malicious?

The following npm versions of ts-wross are flagged malicious: 0.0.8. Treat any of these as compromised.

How do I remediate ts-wross if I installed it?

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

I already installed ts-wross — how do I know if it already compromised me?

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

Is ts-wross part of a known attack campaign?

Yes — ts-wross is associated with the GHSA-53h7-mc3v-w73c, IN-MAL-2026-007271 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find ts-wross across my projects, lockfiles, and CI pipelines?

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

Malicious package

ts-wrossnpm

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

MAL-2026-6278

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall ts-wross

What this malware does

Package is published under the name ts-wross but its package.json claims authorship by Michael Mclaughlin ([email protected]) and points its repository field at https://github.com/MikeMcl/big.js.git, with description and keywords copied from the legitimate big.js arbitrary-precision arithmetic library. The shipped source is a verbatim copy of big.js v7.0.1 with one modification: a try/catch block injected mid-file in both big.js and big.mjs that runs const doc = require("node-slot"); doc.from_str().then(...).catch(...) at module load. Errors are swallowed by the surrounding try/catch so the call is silent. node-slot is declared as a runtime dependency ("node-slot": "^1.0.8") and is therefore pulled in and executed on any require('ts-wross') / import 'ts-wross'. The legitimate big.js has zero dependencies and no such call — the inserted require is a loader trampoline that hands import-time execution on the installer's machine to whatever code node-slot ships. Combined with the impersonated metadata, the package is a lure that drops attacker-controlled code into any consumer that installs it under the assumption it is or relates to big.js.

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

1 flagged

0.0.8

Indicators of compromise (SHA-256)

f2ee248f4b7fad7f6a978fbc5f1accf635566ce61a3ee32f1353eba91bbe42d6

42dae43b7ff77748f10ae5faf6d87b7d63552e5629a37c931ea2c0de3539b469

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ts-wross (version 0.0.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ts-wross across your stack and pipelines.
If you installed it — respond
ts-wross is a typosquat — you almost certainly intended a legitimately-named package. Remove ts-wross, 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 ts-wross 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 ts-wross 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-wross on npm has been identified as a malicious package (version 0.0.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-53h7-mc3v-w73cIN-MAL-2026-007271

References

Credits

Amazon Inspector · finder

Detect & block this

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

Malware detection Runtime egress monitoring