Malicious code in txs-lib-sdk (npm)
Exploitation and risk
Source statusCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
Which CVEs have scores here?
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.
osv · MAL-2026-14198
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (5575013ead36c1ebb523009215200be0a1bf61d21285ca8515573963a63e3aa5) 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. ## Source: ghsa-malware (be8fdee0fed990fd22edd1188e06d7601d45db4031bd545667852f91b8120395) 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.
- Source published
- 19 Aug 2026 01:17:26 UTC
- Source modified
- 30 Sep 2026 01:00:07 UTC
- Saved here
- 24 Oct 2026 13:17:17 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.