Which versions of multica are malicious?

The following npm versions of multica are flagged malicious: 9999.99.99. Treat any of these as compromised.

How do I remediate multica if I installed it?

Remove multica from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound network activity or persistence. Use O3 Security's dependency scanner to confirm the package and its artifacts are fully purged across your stack.

Is multica part of a known attack campaign?

Yes — multica is associated with the IN-MAL-2026-004951, IN-MAL-2026-004952 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

Can O3 Security detect multica in my codebase?

Yes. O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, blocking multica and packages like it before any post-install script runs.

Malicious package

multicanpm

Malicious code in multica (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-5400

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall multica

What this malware does

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.

Malicious versions

1 flagged

9999.99.99

Indicators of compromise (SHA-256)

d7d3e4277fb571072315c7f64c269029cd53c78b3ff27ec5536d748c659fd6a2

ece88aabcd1ebbdef6133024c757b2ce9efa038fabbce6d40ed87f9d60a3a735

Frequently asked questions

No. multica on npm has been identified as a malicious package (version 9999.99.99 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-004951IN-MAL-2026-004952

References

npmjs.com

Credits

Amazon Inspector · finder

Scan your dependencies

O3 Security blocks malicious packages like this at install time and in CI.

Supply-chain protection