mock-transactions-sdk@1.0.1

Summary

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: amazon-inspector (fd727a8b4413f4809193cfac838d9b42ddae62a685086036a026ba2a4e7419e4)