Which versions of karma-proxy are malicious?

The following npm versions of karma-proxy are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate karma-proxy if I installed it?

karma-proxy 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 karma-proxy — how do I know if it already compromised me?

If karma-proxy 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 karma-proxy part of a known attack campaign?

Yes — karma-proxy is associated with the IN-MAL-2026-018384 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 karma-proxy across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for karma-proxy (version 1.0.0).

Malicious package

karma-proxynpm

karma-proxy is a confirmed malicious npm package (MAL-2026-14267) that opens a backdoor for remote access (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in karma-proxy (npm)

MAL-2026-14267

Immediate action

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

npm uninstall karma-proxy

What this malware does

On npm install, the package's postinstall lifecycle script collects host identifiers (os.hostname(), platform, arch, Node.js version, package name, lifecycle event) and POSTs them as JSON to a hardcoded non-first-party endpoint at https://e14giapf.instances.poc.jchunt.top/karma-proxy. The beacon fires unconditionally on every install, with no user opt-in, no configuration, and no disclosure in the package's advertised purpose. The destination is an author-controlled subdomain unrelated to any npm registry or vendor infrastructure.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

379b8e968c18bc5df2f2e00ad56f6c1c139bc97d4a8b19e6d1a917398ad72e58

Detection & response playbook

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for karma-proxy (version 1.0.0).
If you installed it — respond
karma-proxy 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 karma-proxy 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. karma-proxy on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-018384

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks karma-proxy-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