Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

txs-lib-sdknpm

txs-lib-sdk is a confirmed malicious npm package (MAL-2026-14198) that executes malicious code on install (malicious versions 1.0.1, 1.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in txs-lib-sdk (npm)

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

What this malware does

The package's advertised getTransactions() API invokes an internal loader that reads database.js — a file disguised as a product catalog — extracts each record's mark field, base64-decodes it and applies a per-byte Caesar shift, concatenates the result into a code string, and passes it to the Function constructor together with Buffer, require, and process. This yields arbitrary Node.js execution with full filesystem, network, and child_process capabilities on the caller's host whenever the documented API is used. index.js hides the sink by reconstructing the identifiers 'setTimeout', 'Function', 'Buffer', 'require', and 'process' from a split string-array and by resolving the Function constructor indirectly via globalThis.constructor.constructor. The multi-layer obfuscation (identifier reassembly, indirect constructor lookup, base64+Caesar-encoded payload, JSON-shaped carrier file, deferred setTimeout) has no legitimate purpose for a package presented as a transactions helper and is the concealment layer of a supply-chain loader.

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

2 flagged
1.0.11.0.2

Indicators of compromise (SHA-256)

5575013ead36c1ebb523009215200be0a1bf61d21285ca8515573963a63e3aa5
be8fdee0fed990fd22edd1188e06d7601d45db4031bd545667852f91b8120395
092ed7a991ca9ca8d028133dde7e6812ed09fe9a510285127c19c78608a77ac7

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for txs-lib-sdk (2 malicious versions).

  2. If you installed it — respond

    Remove txs-lib-sdk 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.

  3. Did it already run?

    If txs-lib-sdk 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-lib-sdk on npm has been identified as a malicious package (versions 1.0.1, 1.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-018277GHSA-g36j-xxq9-x243IN-MAL-2026-020710

References

Credits

  • Amazon Inspector · finder

Detect & block this

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

Explore

txs-lib-sdk (npm) malicious package — MAL-2026-14198 | O3 Security