NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

txs-runner-libnpm

Advisory published Updated

txs-runner-lib is a confirmed malicious npm package (MAL-2026-11091) that steals credentials and exfiltrates sensitive data (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in txs-runner-lib (npm)

MAL-2026-11091
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall txs-runner-lib

What this malware does

Package [email protected] could not be fully characterized: automated tracing engaged with the package's files but its output was withheld by the provider safety filter, and no a static rule findings are available to corroborate specific behavior. Content-filter suppression on package internals is an atypical outcome for benign libraries and warrants human inspection of the tarball contents before use, but without specific traced code paths or matched patterns, no concrete installer-harm behavior (exfiltration endpoint, credential read, dropper, backdoor) can be named for this version.

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)

23ca04e5d691c417599a28f83df508532ccce1c52a12e5908dd02760d24abdc9
eaf4e668ad1a65cf7be8d260ba2c6ee46a31be7553bad3219775b61a5d226dfc

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for txs-runner-lib (version 1.0.1).

  2. If you installed it — respond

    txs-runner-lib is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

    If txs-runner-lib was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. txs-runner-lib 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-65pq-67vr-g3jpIN-MAL-2026-012898

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks txs-runner-lib-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

txs-runner-lib (npm) malicious package — MAL-2026-11091 | O3 Security