Which versions of notify-theme are malicious?

The following npm versions of notify-theme are flagged malicious: 1.3.5, 1.3.6, 1.3.7. Treat any of these as compromised.

How do I remediate notify-theme if I installed it?

notify-theme establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed notify-theme — how do I know if it already compromised me?

If notify-theme was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is notify-theme part of a known attack campaign?

Yes — notify-theme is associated with the IN-MAL-2026-009654, IN-MAL-2026-009653, IN-MAL-2026-009658 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find notify-theme across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for notify-theme (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging notify-theme across your stack and pipelines.

Malicious package

notify-themenpm

Malicious code in notify-theme (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-10157

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall notify-theme

What this malware does

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.

Malicious versions

3 flagged

1.3.51.3.61.3.7

Indicators of compromise (SHA-256)

7d239abc86d6b02bdc5f88d30fca94ca60124df408762b77df76af4ca4cc5805

a357a8e0ad89f5ad9c14920eecd04d2c1d13e1dfd2ec9399980fe95127f584f4

d9cbb2ac45124e3844e29f3efd70ca26f0089ec4eaad718bcbdaf3035ec9b34b

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for notify-theme (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging notify-theme across your stack and pipelines.
If you installed it — respond
notify-theme establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If notify-theme was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks notify-theme before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. notify-theme on npm has been identified as a malicious package (versions 1.3.5, 1.3.6, 1.3.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-009654IN-MAL-2026-009653IN-MAL-2026-009658

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks notify-theme-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring