Which versions of notify-dist are malicious?

The following npm versions of notify-dist are flagged malicious: 1.3.7. Treat any of these as compromised.

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

Remove notify-dist from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

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

If notify-dist 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-dist part of a known attack campaign?

Yes — notify-dist is associated with the IN-MAL-2026-009651 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-dist 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-dist (version 1.3.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging notify-dist across your stack and pipelines.

Malicious package

notify-distnpm

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

MAL-2026-10154

Immediate action

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

npm uninstall notify-dist

What this malware does

notify-dist advertises itself as a pino-compatible logger/middleware (exports module.exports.pino, keywords fast/logger/stream/json, lib/ mirrors pino internals such as proto.js, multistream.js, redaction.js, transport.js), but the exported middleware's only side effect is to launch a remote-code loader. When a consumer requires the package and invokes the exported middleware, index.js spawns node lib/caller.js as a detached child with stdio: 'ignore' and child.unref() so the loader survives after the parent exits. lib/caller.js issues an HTTP GET to https://jsonkeeper.com/b/BPB86 via axios, reads the .cookie field of the response, and executes it as JavaScript via new Function.constructor('require', s)(require), giving the fetched code full Node privileges including require. The loader retries up to 5 times and silences console.log to hide activity. lib/const.js additionally holds base64-encoded fields that decode to a second endpoint (https://jsonkeeper.com/b/ZK45J) and header name x-secret-key, serving as a rotation/backup payload URL. jsonkeeper.com is a mutable third-party JSON paste host, so the executed code is fully attacker-controlled and can change at any time. The pino-shaped API surface is a lure: consumers importing this expecting logger behavior get arbitrary remote code execution on their machine.

Malicious versions

1 flagged

1.3.7

Indicators of compromise (SHA-256)

1cf89f8fbe4c3f9ae9494077688977f46c8b3f875a552054508ac5eec7b62344

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for notify-dist (version 1.3.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging notify-dist across your stack and pipelines.
If you installed it — respond
Remove notify-dist from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If notify-dist 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-dist 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-dist on npm has been identified as a malicious package (version 1.3.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-009651

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks notify-dist-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring