# MAL-2026-14268: Malicious code in no-for-of-loops (npm)


- **Type:** Malicious package
- **Package:** `no-for-of-loops` (npm)
- **Published:** 19 Aug 2026
- **Also known as:** GHSA-hfg2-857w-8wm9

## What is MAL-2026-14268?

MAL-2026-14268 is a malicious package in no-for-of-loops, published on 19 Aug 2026. 

### Official description

package.json declares no-for-of-loops as its own dependency and devDependency, with the source pointed at http://pack.nppacks.com/npm/no-for-of-loops instead of the npm registry. On `npm install`, npm fetches a tarball from this host over unauthenticated plain HTTP with no integrity hash, and installs its contents into the consumer's node_modules. The domain operator can serve arbitrary, mutable bytes on each fetch, meaning any code shipped from that host runs inside the installer's dependency tree. The main module's header additionally self-identifies the package as a 'Security Research Testing Purpose' artifact, and the package description is a bare 'NPM', consistent with a hijack-vector proof-of-concept rather than a functional utility. The auto-execute condition is satisfied: any default `npm install` of this package resolves and installs the attacker-controlled tarball without user opt-in.

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

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-14268 is a malicious package: no-for-of-loops (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-14268/ (Markdown: https://insights.sbomify.com/MAL-2026-14268/index.md)
```

## Sources

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

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