Which versions of magika-js are malicious?

The following npm versions of magika-js are flagged malicious: 4.1.1. Treat any of these as compromised.

How do I remediate magika-js if I installed it?

magika-js establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed magika-js — how do I know if it already compromised me?

If magika-js was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is magika-js part of a known attack campaign?

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

How do I find magika-js across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for magika-js (version 4.1.1).

Malicious package

magika-jsnpm

magika-js is a confirmed malicious npm package (MAL-2026-14247) that opens a backdoor for remote access (malicious version 4.1.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in magika-js (npm)

MAL-2026-14247

Immediate action

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

npm uninstall magika-js

What this malware does

magika-js is a typosquat of Google's magika library. The postinstall lifecycle script collects installer host identifiers (hostname, platform, arch, node version, package name, npm lifecycle event, timestamp) and POSTs them as JSON to the hardcoded endpoint https://ucjtw03t.instances.poc.jchunt.top/magika-js. The beacon fires automatically on npm install with no opt-in and no documented purpose served by the transmission, sending installer machine data to a non-publisher domain. A source.txt pointer to github.com/google/magika reinforces the impersonation of Google's project.

Malicious versions

1 flagged

4.1.1

Indicators of compromise (SHA-256)

41cd28e41bc842fd046a2bff254f450edd0b6d2d15d961fe768cf5e9ebfa197f

Detection & response playbook

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for magika-js (version 4.1.1).
If you installed it — respond
magika-js establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If magika-js was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

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

Campaign

IN-MAL-2026-018345

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks magika-js-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database