block-slot (npm) · Malicious Code

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (c9443517fbcf695478ab489e9a375823ed1a0030cf6a3a4f6262effca4c5406b) Pattern matches fired on index.js for the co-occurrence of child_process require, HTTP GET calls, and env-related keywords within a single file. No traced code path was confirmed to perform exfiltration, install-time fetch-and-execute, silent-relay, or credential harvesting. The matches may reflect benign composition (e.g., a CLI that spawns subprocesses and makes outbound HTTP requests for documented purposes), but the bundle's intent could not be verified from pattern signals alone. A human reviewer should de-minify or read index.js to confirm whether the HTTP destinations are attacker-controlled, whether process.env contents are sent outbound, and whether any of this fires at install/require time versus only on explicit CLI invocation. ## Source: ghsa-malware (45d25c6b3ae56eaaf7f76995fc0b6f93a8499b9cbe2315446a63cb5601d841d4) 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.

• github.com/advisories/GHSA-pg29-x97h-gfr6 (opens in a new tab)
• npmjs.com/package/block-slot/v/1.0.9 (opens in a new tab)