Which versions of ts-tweetnacl are malicious?

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

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

Remove ts-tweetnacl 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-tweetnacl — how do I know if it already compromised me?

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

Yes — ts-tweetnacl is associated with the GHSA-vj23-9g2p-fvww 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-tweetnacl 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-tweetnacl (version 0.1.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ts-tweetnacl across your stack and pipelines.

Malicious package

ts-tweetnaclnpm

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

MAL-2026-247

Immediate action

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

npm uninstall ts-tweetnacl

What this malware does

The package ts-tweetnacl was found to contain malicious code.

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.

The OpenSSF Package Analysis project identified 'ts-tweetnacl' @ 0.1.3 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

0.1.3

Indicators of compromise (SHA-256)

b973890e15f6ac1525c83a046da3e3f20503a3c32b03759856ac14bad807e5b8

1fc02aaeff144bdf5547d650cfae75b4f8861d765cafa72a8bd01609b8be299b

b8c7022964715c8d5771f3663406b7b80018244bca155ecad7064ba3d2b2ce5e

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-tweetnacl (version 0.1.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ts-tweetnacl across your stack and pipelines.
If you installed it — respond
Remove ts-tweetnacl 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-tweetnacl 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-tweetnacl 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-tweetnacl on npm has been identified as a malicious package (version 0.1.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-vj23-9g2p-fvww

References

github.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

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