# MAL-2026-17336: Malicious code in @redman89405/my-module (npm)


- **Type:** Malicious package
- **Package:** `@redman89405/my-module` (npm)
- **Published:** 30 Sep 2026
- **Also known as:** GHSA-vc53-jhh2-pwf3

## What is MAL-2026-17336?

MAL-2026-17336 is a malicious package in @redman89405/my-module, published on 30 Sep 2026. 

### Official description

The package ships `code.png` alongside `index.js` and exports a function `imageToCode` that reads a length-prefixed byte stream from the first pixel row of the PNG and passes the decoded string to `Function(...)()`, an eval-equivalent sink. The executable content is hidden inside an image asset rather than present as readable source, so the code that will run cannot be seen by inspecting the npm tarball. The API is exported alongside trivial `hello`/`add` helpers with no documented purpose for image-based code loading, and the author retains the ability to change the payload in future publishes without any visible source diff. The code path relies on browser-only globals (Image, canvas) so it does not fire on Node `require`; harm requires a consumer application to call `imageToCode` in a browser context, at which point arbitrary author-supplied JavaScript executes in that page.

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

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-17336 is a malicious package: @redman89405/my-module (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-17336/ (Markdown: https://insights.sbomify.com/MAL-2026-17336/index.md)
```

## Sources

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

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