MAL-2026-17767 Malicious code in another-very-long-name (npm)
Malicious package
Published
MAL-2026-17767 is a malicious package: another-very-long-name (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-17767/ (Markdown: https://insights.sbomify.com/MAL-2026-17767/index.md)
- Package
- another-very-long-name
- Registry
- npm
What is MAL-2026-17767?
MAL-2026-17767 is a malicious package in another-very-long-name, published on 11 Oct 2026.
Official description
[email protected] ships a beacon.cjs that is invoked both from the declared postinstall lifecycle script and from the module's require()-time entry (index.js). On execution it collects host identifiers — hostname, install path, process.cwd(), process.version, OS metadata, and the package name — and POSTs them as JSON to the hardcoded cleartext endpoint http://185.158.107.175:8787/_ah/dc. The package exposes no genuine functionality: index.js returns a Proxy whose get handler returns a no-op for every property so that bundlers consuming the package do not fail, and an author comment states that a build that completes and calls back is cleaner evidence. The destination is a bare-IP HTTP endpoint with no first-party relationship to any declared publisher, and the stub-plus-beacon shape is consistent with a dependency-confusion reconnaissance probe rather than a compatibility shim.
What should I do about MAL-2026-17767?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.