MAL-2026-17778 Malicious code in some-very-long-package-name (npm)
Malicious package
Published
MAL-2026-17778 is a malicious package: some-very-long-package-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-17778/ (Markdown: https://insights.sbomify.com/MAL-2026-17778/index.md)
- Package
- some-very-long-package-name
- Registry
- npm
What is MAL-2026-17778?
MAL-2026-17778 is a malicious package in some-very-long-package-name, published on 11 Oct 2026.
Official description
The package is a stub whose main module exports a Proxy that returns a no-op for every property access, providing none of the functionality implied by the package name or its 'compatibility shim' description. Its only real behavior is beacon.cjs, which collects host and install identifiers (hostname, install path, process.cwd(), process.version, package name/user-agent) and POSTs them to the hardcoded bare-IP HTTP endpoint http://185.158.107.175:8787/_ah/dc. The beacon fires both automatically at install time via scripts.postinstall and again when the module is loaded via require(), because index.js invokes beacon.fire(). The shape — stub module, hardcoded non-DNS bare-IP C2 over plain HTTP, collection of installer host identifiers at install and require time — is consistent with a dependency-confusion / internal-name-squat reconnaissance beacon reporting successful installation inside private build environments.
What should I do about MAL-2026-17778?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.