# MAL-2026-6416: Malicious code in block-slot (npm)


- **Type:** Malicious package
- **Package:** `block-slot` (npm)
- **Published:** 25 Jun 2026
- **Also known as:** GHSA-pg29-x97h-gfr6

## What is MAL-2026-6416?

MAL-2026-6416 is a malicious package in block-slot, published on 25 Jun 2026. 

### Official description

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.

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.

## What should I do about MAL-2026-6416?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-6416 is a malicious package: block-slot (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-6416/ (Markdown: https://insights.sbomify.com/MAL-2026-6416/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-6416

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-6416/
Summaries are generated and may contain mistakes; the official description above is the record.