MAL-2026-3748 Malicious code in @pelmnaads/naads-common-logger (npm)
Malicious package
Published
MAL-2026-3748 is a malicious package: @pelmnaads/naads-common-logger (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-3748/ (Markdown: https://insights.sbomify.com/MAL-2026-3748/index.md)
- Package
- @pelmnaads/naads-common-logger
- Registry
- npm
What is MAL-2026-3748?
MAL-2026-3748 is a malicious package in @pelmnaads/naads-common-logger, published on 14 May 2026.
Official description
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.What should I do about MAL-2026-3748?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.