MalwarePublished 9 Jul 2026

txs-builder-lib (npm) · Malicious Code

Affects txs-builder-libSource GCVE Database

Malicious package : remove txs-builder-lib and rotate any secrets on hosts that installed it.

Data as of 11 Jul 2026, 09:43 UTC

Classification

Malicious package

Published to npm · OSV MAL-2026-10021

What to do

Remove txs-builder-lib from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.

Affected software

Product	Affected	Fixed in
npmtxs-builder-lib	Affected =1.0.2 =1.0.1 =1.0.3	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (55bb13d76ebc74c36f68dd219079500d0bdb60e4bc07f8089eefbcde91bbdeac) The package was found to contain malicious code or consuming dependency that contains malicious code ## Source: ghsa-malware (a6bc668268806a7a1e0cc6b81ae98e0ea47e0dff4f43f5da252255557cbe3abe) 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.

Impact

Systems with txs-builder-lib versions 1.0.1, 1.0.2, or 1.0.3 installed are at risk of full compromise. Attackers may have gained complete control over the affected computer, potentially exposing all stored secrets and keys. This level of compromise can lead to unauthorized access, data theft, and further malicious activities. The presence of malicious code in the package means that the integrity and confidentiality of the system are severely impacted.

Defensive guidance

Remove the txs-builder-lib package versions 1.0.1, 1.0.2, and 1.0.3 immediately from affected systems. Rotate all secrets and keys stored on the compromised computer from a separate, secure device. Because full control of the system may have been given to an attacker, consider rebuilding or fully reimaging the affected system to ensure complete removal of malicious software. Monitor for any signs of persistent compromise.

Summary

The txs-builder-lib npm package versions 1.0.1, 1.0.2, and 1.0.3 have been identified as containing malicious code or relying on a dependency that contains malicious code. According to sources including Amazon Inspector and the GitHub Security Advisory for malware, any system with this package installed or running should be considered fully compromised. The malicious code presence implies that attackers may have gained full control over the system, necessitating immediate secret and key rotation from a secure environment. Removal of the package alone does not guarantee eradication of the malware due to potential persistence mechanisms.

References

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 10 Jul 2026, 09:37 UTC

Technical details

References

Community reviews