Which versions of @pelmnaads/naads-common-logger are malicious?

The following npm versions of @pelmnaads/naads-common-logger are flagged malicious: 19999.0.1. Treat any of these as compromised.

How do I remediate @pelmnaads/naads-common-logger if I installed it?

Remove @pelmnaads/naads-common-logger 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 @pelmnaads/naads-common-logger — how do I know if it already compromised me?

If @pelmnaads/naads-common-logger 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 @pelmnaads/naads-common-logger part of a known attack campaign?

Yes — @pelmnaads/naads-common-logger is associated with the IN-MAL-2026-002766, IN-MAL-2026-002763, IN-MAL-2026-002786 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 @pelmnaads/naads-common-logger 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 @pelmnaads/naads-common-logger (version 19999.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @pelmnaads/naads-common-logger across your stack and pipelines.

Malicious package

@pelmnaads/naads-common-loggernpm

Malicious code in @pelmnaads/naads-common-logger (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-3748

Immediate action

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

npm uninstall @pelmnaads/naads-common-logger

What this malware does

The package is published to the public npm registry under @pelmnaads/naads-common-logger with version 19999.0.1 — the canonical dependency-confusion pattern, where an abnormally high version is used to make npm's resolver prefer this public package over a private internal package of the same name. On npm install, a preinstall lifecycle script (preinstall.js:5-9) makes an HTTPS GET to h5nvwrz2815ubw84cpkwhezm5db9z1nq.b.mburpcollab.com with query parameters package=<npm_package_name>&hostname=<os.hostname()>, transmitting the installer's hostname off-host to a Burp Collaborator out-of-band interaction endpoint. The README states this is an authorized security test, but the code path and effect on an unsuspecting installer are identical to a hostile dependency-confusion attack: build hosts silently disclose their identity to a third-party domain during npm install, with no opt-in. Any build system that resolves this package (e.g., an internal Pelmorex pipeline expecting the private @pelmnaads/naads-common-logger) would leak hostname data.

Malicious versions

1 flagged

19999.0.1

Indicators of compromise (SHA-256)

2f25d490deb5c32e9675f7941c54e8e9c9c1c180adaf00de19e4bb2a10325c47

68990dfacdc750bf464d646aca4855c2dd23bbefcadef1d9638e2d663a23fc57

8e4fd2828e3ff35aa485baef1b289b8faa19386e1c5199cbddb213b844a57733

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 @pelmnaads/naads-common-logger (version 19999.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @pelmnaads/naads-common-logger across your stack and pipelines.
If you installed it — respond
Remove @pelmnaads/naads-common-logger 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 @pelmnaads/naads-common-logger 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 @pelmnaads/naads-common-logger 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. @pelmnaads/naads-common-logger on npm has been identified as a malicious package (version 19999.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-002766IN-MAL-2026-002763IN-MAL-2026-002786

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @pelmnaads/naads-common-logger-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