# MAL-2026-18341: Malicious code in macro-kernel-record-reader (npm)


- **Type:** Malicious package
- **Package:** `macro-kernel-record-reader` (npm)
- **Published:** 27 Oct 2026
- **Also known as:** GHSA-32g3-f74c-pcxq

## What is MAL-2026-18341?

MAL-2026-18341 is a malicious package in macro-kernel-record-reader, published on 27 Oct 2026. 

### Official description

package.json declares its sole dependency `cache-locale-runner-writer` as an arbitrary HTTPS tarball URL (`https://artifacts.creditslib.com/npm/cache-locale-runner-writer`) instead of a registry version range. On `npm install`, npm fetches whatever bytes that URL serves and installs them, with no version pin, no integrity hash, and no signature check. Any lifecycle scripts in the fetched tarball run on the installer's machine, and the shipped `index.js` is a thin stub that re-exports the fetched dependency, so `require()` of this package loads the off-registry code at runtime as well. The host `artifacts.creditslib.com` is unrelated to the declared repository and is fully controlled by whoever operates it, who can serve different bytes to different installers or change the payload at any time.

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

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-18341 is a malicious package: macro-kernel-record-reader (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-18341/ (Markdown: https://insights.sbomify.com/MAL-2026-18341/index.md)
```

## Sources

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

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