MAL-2026-5400 Malicious code in multica (npm)
Malicious package
Published
MAL-2026-5400 is a malicious package: multica (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-5400/ (Markdown: https://insights.sbomify.com/MAL-2026-5400/index.md)
- Package
- multica
- Registry
- npm
What is MAL-2026-5400?
MAL-2026-5400 is a malicious package in multica, published on 9 Jun 2026.
Official description
Package is published at version 9999.99.99 with a description referencing an npm 404 in multica-ai/multica and a main module that recursively requires
multica itself — the canonical shape of a dependency-confusion probe designed to win resolution against an internal package of the same name. On npm install, postinstall.js unconditionally POSTs a JSON payload containing the package name/version, Node version, OS platform, timestamp, detected CI vendor (selected from a list of 12 CI environment variables), and — when set — GITHUB_REPOSITORY, GITHUB_REPOSITORY_OWNER, and GITHUB_WORKFLOW to https://ddactic-lab.online/sc/beacon. A DNS fallback channel encodes a package slug, CI slug, and hash into a subdomain of b.ddactic-lab.online to bypass HTTP-blocking egress proxies. Installer harm: silent disclosure of internal package names, CI vendor, and GitHub org/repo/workflow identifiers to an attacker-controlled endpoint at install time, mapping which organizations resolve internal names to this public tarball.What should I do about MAL-2026-5400?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.