Which versions of prokit-core are malicious?

The following npm versions of prokit-core are flagged malicious: 20.6.6. Treat any of these as compromised.

How do I remediate prokit-core if I installed it?

Remove prokit-core 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 activity or persistence.

I already installed prokit-core — how do I know if it already compromised me?

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

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

Search your lockfiles and build artifacts for prokit-core (version 20.6.6).

Malicious package

prokit-corenpm

Advisory published Aug 5, 2026Updated Aug 5, 2026

prokit-core is a confirmed malicious npm package (MAL-2026-12420) that executes malicious code on install (malicious version 20.6.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in prokit-core (npm)

MAL-2026-12420

Immediate action

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

npm uninstall prokit-core

What this malware does

On require of the package, index.js unconditionally loads helpers.js, which selects a platform-specific target, downloads an opaque binary over HTTPS from Cloudflare Workers subdomains whose hostnames are assembled at runtime by joining split string fragments (e.g. oob-worker.cf101-adf.workers.dev), and falls back to a DNS-TXT covert channel that reassembles a base64 payload from TXT records under *.dl.well1.site (tin.dl.well1.site, ldr.dl.well1.site, win.dl.well1.site, tina.dl.well1.site). The retrieved bytes are written to /var/tmp or %TEMP% under a disguised name (.cache<hex> on Unix, dotnet_diag_<hex>.exe on Windows), chmod 0755, and spawned detached via /bin/sh -c or cmd.exe. A /tmp/.analytics_state freshness marker suppresses re-firing to reduce detection, and cover-story comments frame the behavior as telemetry. Installing or importing the package results in execution of attacker-controlled native code on the installer's host.

Malicious versions

1 flagged

20.6.6

Indicators of compromise (SHA-256)

8d1f094f3b3aea4e6c087847823efe5c1f1a930ac746aa2696259951e6332f92

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for prokit-core (version 20.6.6).
If you installed it — respond
Remove prokit-core 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 activity or persistence.
Did it already run?
If prokit-core 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. prokit-core on npm has been identified as a malicious package (version 20.6.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014790

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks prokit-core-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database