Which versions of txs-data are malicious?

The following npm versions of txs-data are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate txs-data if I installed it?

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

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

Yes — txs-data is associated with the GHSA-w5pf-vc8f-rv6r, IN-MAL-2026-008893 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 txs-data 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 txs-data (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging txs-data across your stack and pipelines.

Malicious package

txs-datanpm

txs-data is a confirmed malicious npm package (MAL-2026-6900) that executes malicious code on install (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in txs-data (npm)

MAL-2026-6900

Immediate action

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

npm uninstall txs-data

What this malware does

The package was found to contain malicious code or consuming dependency that contains 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.

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

9035aa8112e58acf7cb81f402e63fffaccbcc29d77d8b426c9e9086f8969acda

74154a8e4e769872929446eb17b4dc59a1b491508c7bd05e55d1cdb232ecf2aa

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

Campaign

GHSA-w5pf-vc8f-rv6rIN-MAL-2026-008893

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks txs-data-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