txs-runner-sdknpm
txs-runner-sdk is a confirmed malicious npm package (MAL-2026-14199) that executes malicious code on install (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in txs-runner-sdk (npm)
What this malware does
The package advertises itself as generating random transaction data, but its main API method getTransactions() invokes load_transaction_data(), which reads database.js (a JSON file whose records carry base64-encoded 'mark' fields), applies a per-character Caesar shift keyed by an item count, base64-decodes the concatenated result, and passes the resulting bytes to eval() inside a try/catch. The.js-suffixed data file, the double-encoded payload smuggled as product 'mark' fields, and the mismatch between the stated purpose (random data generation) and the presence of dynamic code execution together form a loader/dropper pattern: any consumer that calls the advertised API executes attacker-authored JavaScript in the calling process. Declared dependencies include axios and python-shell, consistent with a stager that fetches or spawns further payloads once the decoded code runs.
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-runner-sdk (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging txs-runner-sdk across your stack and pipelines.
If you installed it — respond
Remove txs-runner-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-runner-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-runner-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-runner-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.