CRITICAL npm Malware

Malicious code in txs-random-lib (npm)

MAL-2026-11090 · GHSA-c2fc-52mv-g5v6

Published · Modified

Dependency scanning

Check whether txs-random-lib is in your codebase

Corgea flags malicious and compromised dependencies with reachability analysis, so you fix the packages that actually run in your application instead of working through the whole lockfile.

Description


__

Source: amazon-inspector (a9f40781ae94116a5e9e1fb190897b78899c9e66abd10f1eb63216b78e986953)

Package txs-random-lib@1.0.1 was inspected but no concrete a static rule matches or traced-code findings are available for this verdict. The behavioral trace engaged with the package's files but its output was withheld by the model provider's safety filter, which typically triggers on content resembling operational malware (credential theft, exfiltration primitives, shell/remote-execution code). Without corroborated behavioral evidence naming a specific data read, destination, or execution primitive, the package's actual behavior cannot be described from the available signals. The name pattern and absence of any observable legitimate purpose in what was scanned leave the disposition ambiguous.

Source: ghsa-malware (b2fbf9f715398c5e2041d0bca1412ae9a5eb94d025e289b02c3ad808ecdd9d9f)

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.

Ready to move

Start Securing

Free, no credit card | First findings in minutes