Malicious code in block-slot (npm)
--- _-= 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.
AI Analysis
Technical Summary
The 'block-slot' npm package version 1.0.9 has been identified as malicious. Static analysis revealed code patterns involving subprocess spawning, outbound HTTP requests, and environment variable usage within a single file (index.js). Although no explicit code path was confirmed to perform data exfiltration or credential theft, the package's presence implies full compromise of the host system. The advisory recommends treating any system with this package installed as fully compromised, necessitating secret rotation and package removal. No patch or fix is available, and no known exploits in the wild have been reported.
Potential Impact
Any computer with 'block-slot' version 1.0.9 installed or running is considered fully compromised. Attackers may have gained full control, risking exposure of all stored secrets and keys. Removal of the package alone does not guarantee eradication of malicious software introduced by it.
Mitigation Recommendations
Remove the 'block-slot' package version 1.0.9 immediately from all affected systems. Rotate all secrets and keys from a separate, trusted computer to prevent further compromise. Since no official patch or fix is available, these steps are critical to mitigate the threat.
Malicious code in block-slot (npm)
Description
--- _-= 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.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The 'block-slot' npm package version 1.0.9 has been identified as malicious. Static analysis revealed code patterns involving subprocess spawning, outbound HTTP requests, and environment variable usage within a single file (index.js). Although no explicit code path was confirmed to perform data exfiltration or credential theft, the package's presence implies full compromise of the host system. The advisory recommends treating any system with this package installed as fully compromised, necessitating secret rotation and package removal. No patch or fix is available, and no known exploits in the wild have been reported.
Potential Impact
Any computer with 'block-slot' version 1.0.9 installed or running is considered fully compromised. Attackers may have gained full control, risking exposure of all stored secrets and keys. Removal of the package alone does not guarantee eradication of malicious software introduced by it.
Mitigation Recommendations
Remove the 'block-slot' package version 1.0.9 immediately from all affected systems. Rotate all secrets and keys from a separate, trusted computer to prevent further compromise. Since no official patch or fix is available, these steps are critical to mitigate the threat.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-6416
- Osv Schema Version
- 1.7.4
- Aliases
- ["GHSA-pg29-x97h-gfr6"]
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a50ba5068715ace4357ebd4
Added to database: 07/10/2026, 09:24:32 UTC
Last enriched: 07/10/2026, 09:41:13 UTC
Last updated: 07/24/2026, 02:45:11 UTC
Views: 13
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.