Which versions of ts-opus are malicious?

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

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

Remove ts-opus from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

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

If ts-opus 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-opus part of a known attack campaign?

Yes — ts-opus is associated with the IN-MAL-2026-007524, GHSA-xr76-fgrm-h52p 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-opus 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-opus (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-opus across your stack and pipelines.

Malicious package

ts-opusnpm

ts-opus is a confirmed malicious npm package (MAL-2026-6468) that executes malicious code on install (malicious version 0.0.8). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ts-opus (npm)

MAL-2026-6468

Immediate action

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

npm uninstall ts-opus

What this malware does

ts-opus 0.0.8 ships an unmodified copy of MikeMcl/big.js (README, copyright, and repository URL all reference big.js) but injects an additional top-level block inside both big.js and big.mjs that calls require('node-slot') and invokes doc.from_str(), with both the synchronous error and the returned promise's rejection silently swallowed (try {....then(e=>{}).catch(e=>{}) } catch(error){}). The required module name node-slot is not declared in package.json — the declared dependency is the differently-named ref-slot — so the code intentionally loads an externally-resolved package whose contents are not controlled by this tarball. Any consumer who require('ts-opus') or imports big.mjs triggers loading and executing whatever node-slot resolves to at install time, with failures hidden from the user. The combination of (a) a cover-story package presenting itself as big.js, (b) require-time execution of an undeclared external module, and (c) silenced error handling to hide payload failures is a targeted supply-chain attack against consumers who believe they are pulling in 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)

73b0105b34723dd6e1449c3353d1d4df0dcf94ae460a4dfd156566bb4ba372c7

823418ded09f0da1edeb47585ca94c75449607a5e7661c52ab136f0b0b872bf2

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ts-opus (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-opus across your stack and pipelines.
If you installed it — respond
Remove ts-opus from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If ts-opus 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-opus 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-opus 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

IN-MAL-2026-007524GHSA-xr76-fgrm-h52p

References

Credits

Amazon Inspector · finder

Detect & block this

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

Explore

All malware advisories How O3 detects malware Vulnerability database