This report shows the evidence for mock-data-sdk@1.0.1. 1 of 3 known versions is blocked or flagged. The newest version, 0.0.1-security, is allowed.
Blocked by malware advisory
OpenSSF/OSV malware advisory MAL-2026-19143 identifies this version as malicious and supplies the Firewall block. LPM AI assessed this version as suspicious; the assessments disagree.
What to do: remove this version and, if it ran, rotate the credentials it could reach. Remediation↓
OpenSSF/OSV malicious advisory
published · by OpenSSF/OSV
OpenSSF/OSV advisory MAL-2026-19143 confirms this npm version as malicious.
Advisory
MAL-2026-19143
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in mock-data-sdk (npm)
Details
The package presents itself as a mock-data generator but hides a base64-encoded JavaScript payload across the `mark` fields of data/products_*.js. The library entrypoint (index.js) concatenates those fields, decodes the result with Buffer.from(..., 'base64').toString('utf-8'), and executes it via the Function() constructor with Buffer, require, and process passed in as arguments. The identifiers 'Buffer', 'require', 'process', and 'new Function' are reconstructed at runtime from an XOR-obfuscated table keyed by a derived 4-byte seed, which conceals the eval sink from string-based scanners. The exported getTransactions() API triggers this execution on every call. The decoded payload loads python-shell and https, writes a Python script to /tmp/targets, and recursively walks the filesystem (pathlib.Path(root).rglob('*')) for file names containing 'password', 'wallet', 'seed', 'privatekey', or '.env'. The advertised purpose (mock data) has no legitimate need to enumerate credential-, wallet-, and dotenv-shaped files on the installer's host or to run arbitrary code reconstructed from pseudo-data files.
LPM's AI review found this version suspicious. That disagrees with the OpenSSF/OSV advisory, which supplies the block.
The transaction API automatically executes code concealed in data-file fields, with access to Node.js capabilities. The payload’s purpose is unclear, so this is suspicious rather than a confirmed attack.
Static reason
No blocking static signals were detected.
Trigger
Calling `getTransactions`; no separate request is needed for its internal payload execution.
Impact
The concealed code can perform runtime actions with the package process's available Node.js capabilities; its actual effects are unknown.
Mechanism
The method calls `get_transfer_data`, which concatenates `mark` fields from `data/`, base64-decodes the result, and evaluates it with access to `require` and `process`. The payload's purpose could not be established from the inspected excerpts.
The versions list below shows the verdict for each recorded version.
Avoid installing mock-data-sdk@1.0.1. Remove it from direct dependencies and check your lockfile for transitive copies.
Choose an independently verified alternative or release. This report does not establish that other versions are safe.
If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.