Malicious code in mock-transactions-sdk (npm)

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (fd727a8b4413f4809193cfac838d9b42ddae62a685086036a026ba2a4e7419e4) The package presents itself as a mock-transaction data generator but ships a dynamic-code loader. index.js builds the identifiers 'setTimeout', 'Function', 'Buffer', 'require', and 'process' by index-combining fragments of a string array and resolves the Function constructor indirectly through (function(){return this}).constructor.constructor. The documented getTransactions() entry point calls load_transaction_data(count), which concatenates the base64 `mark` fields from database.js, Caesar-shifts the result by count % 256, base64-decodes it, passes the decoded bytes to the reassembled Function constructor with Buffer, require, and process bound as arguments, and invokes the resulting function (deferred via setTimeout). package.json additionally declares python-shell, base-64, and axios as dependencies, none of which are referenced by the shipped source — these modules are reachable only through the require handle passed into the decoded payload, pre-provisioning an HTTP client and a Python subprocess runner for the executed blob. Any consumer that invokes the advertised getTransactions API therefore runs attacker-authored JavaScript on the installer's host with full Node capabilities, with the payload content controlled by the author through database.js. The identifier obfuscation, indirect Function-constructor resolution, Caesar+base64 payload encoding, and capability-pre-provisioned-but-unreferenced dependencies together are a deliberate loader, not instrumentation. ## Source: ghsa-malware (ea0afdca00ff4ca41369f7486274b781a6d79f8ee58da107346a729ef3e849fb) 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

28 Oct 2026 16:54:25 UTC

Source modified

29 Oct 2026 13:48:10 UTC

Observed here

29 Oct 2026 14:12:32 UTC

Source terms

OSV · upstream source license applies

Original source record · Cite this exact observation · Complete original publisher JSON

This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: osv · OSV · upstream source license applies. Source text is retained; field grouping and change labels are provided by ChangeIntel.