MAL-2026-18105 Malicious code in @securihackbot/depconf-stage-1792484738 (npm)
Malicious package
Published
MAL-2026-18105 is a malicious package: @securihackbot/depconf-stage-1792484738 (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-18105/ (Markdown: https://insights.sbomify.com/MAL-2026-18105/index.md)
- Package
- @securihackbot/depconf-stage-1792484738
- Registry
- npm
What is MAL-2026-18105?
MAL-2026-18105 is a malicious package in @securihackbot/depconf-stage-1792484738, published on 20 Oct 2026.
Official description
The package's npm postinstall hook automatically executes on install and transmits installer-identifying data to a hardcoded remote endpoint. It collects os.hostname(), the local username, platform/arch, Node version, package name, and a nonce, base64-encodes the payload, and sends it as a
d= query parameter via plain-HTTP GET to http://34.143.131.27:18080/x-VA-1/main.js (overridable only via a DEPCONF_CALLBACK_URL env var that defaults to this hardcoded bare IP). A DNS beacon fallback to a configurable collaborator suffix is also issued. The package name (@securihackbot/depconf-stage-...) and bundled configure.sh workflow are structured to be re-published under victim-internal scopes so that npm install of an internal package name resolves to this artifact from the public registry, at which point the postinstall beacon fires and leaks the host, user, and internal package name back to the operator — a dependency-confusion attack payload against any environment that resolves it.What should I do about MAL-2026-18105?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.