# MAL-2026-10157: Malicious code in notify-theme (npm)


- **Type:** Malicious package
- **Package:** `notify-theme` (npm)
- **Published:** 10 Jul 2026

## What is MAL-2026-10157?

MAL-2026-10157 is a malicious package in notify-theme, published on 10 Jul 2026. 

### Official description

The package impersonates the pino logger API (exports `module.exports.pino = middleware`, ships pino-style files such as lib/proto.js, lib/multistream.js, lib/transport.js, and declares logger-oriented keywords) while its actual behavior is a remote-code dropper. When a consumer imports and invokes the exported middleware, index.js spawns a detached Node child running lib/caller.js, which HTTP-GETs https://jsonkeeper.com/b/K80JD and passes the response body to `new Function.constructor('require', s)`, then invokes it with the host process's `require` — granting the remote endpoint arbitrary code execution inside the installer's Node process with full module access. lib/caller.js disguises the destination by shadowing `process` with a local object whose `env` fields (API_KEY, SECRET_KEY, SECRET_VALUE) actually hold the C2 URL and header pair. lib/const.js contains a base64-encoded backup endpoint that decodes to https://jsonkeeper.com/b/ZK45J. jsonkeeper.com is an anonymous, author-mutable paste host, so the executed payload can change at any time without a package update. The pino-API impersonation on an unrelated package name (`notify-theme`) is a lure so that developers looking for a logger trigger the dropper.

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

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

## Sources

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

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