Which versions of txs-builder-lib are malicious?

The following npm versions of txs-builder-lib are flagged malicious: 1.0.2. Treat any of these as compromised.

How do I remediate txs-builder-lib if I installed it?

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

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

Yes — txs-builder-lib is associated with the GHSA-r4hr-3frr-jgjv, IN-MAL-2026-009437 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-builder-lib 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-builder-lib (version 1.0.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging txs-builder-lib across your stack and pipelines.

Malicious package

txs-builder-libnpm

Malicious code in txs-builder-lib (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-10021

Immediate action

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

npm uninstall txs-builder-lib

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.2

Indicators of compromise (SHA-256)

a6bc668268806a7a1e0cc6b81ae98e0ea47e0dff4f43f5da252255557cbe3abe

55bb13d76ebc74c36f68dd219079500d0bdb60e4bc07f8089eefbcde91bbdeac

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

Campaign

GHSA-r4hr-3frr-jgjvIN-MAL-2026-009437

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks txs-builder-lib-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