txs-lib-sdknpm
txs-lib-sdk is a confirmed malicious npm package (MAL-2026-14198) that executes malicious code on install (malicious version 1.0.2). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in txs-lib-sdk (npm)
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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for txs-lib-sdk (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-lib-sdk across your stack and pipelines.
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.
Did it already run?
If txs-lib-sdk 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-lib-sdk 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
Campaign
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.