# MAL-2026-10435: Malicious code in fetchcraft (npm)


- **Type:** Malicious package
- **Package:** `fetchcraft` (npm)
- **Published:** 13 Jul 2026
- **Also known as:** GHSA-fg76-g9g4-9xpr

## What is MAL-2026-10435?

MAL-2026-10435 is a malicious package in fetchcraft, published on 13 Jul 2026. 

### Official description

package.json declares the runtime dependency `node-runtime-utils` as `https://github.com/Hexa-devy/node-runtime-utils/archive/refs/heads/main.tar.gz` — a tarball fetched from the mutable `main` branch of a personal GitHub user's repository, with no commit SHA, tag, or integrity hash pinning. On `npm install fetchcraft`, npm downloads and installs whatever bytes that URL serves at install time, including any lifecycle scripts (preinstall/install/postinstall/prepare) shipped in the fetched tarball. Because the source is a mutable branch under a personal account rather than a registry-published package or a pinned commit, the contents can be swapped at any time without any change to fetchcraft itself, allowing arbitrary code to be executed on the installer's machine. The dependency is not referenced by the package's exported code, giving it no legitimate functional purpose.

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-10435?

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-10435 is a malicious package: fetchcraft (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-10435/ (Markdown: https://insights.sbomify.com/MAL-2026-10435/index.md)
```

## Sources

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

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