Which versions of kreactjs are malicious?

The following npm versions of kreactjs are flagged malicious: 1.1.2, 1.1.4, 8.7.6. Treat any of these as compromised.

How do I remediate kreactjs if I installed it?

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

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

Yes — kreactjs is associated with the RLMA-2026-05135, RLUA-2026-06297 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 kreactjs across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for kreactjs (3 malicious versions).

Malicious package

kreactjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

kreactjs is a confirmed malicious npm package (MAL-2026-7307) that executes malicious code on install (malicious versions 1.1.2, 1.1.4, 8.7.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in kreactjs (npm)

MAL-2026-7307

Immediate action

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

npm uninstall kreactjs

Malicious versions

3 flagged

1.1.21.1.48.7.6

Indicators of compromise (SHA-256)

f1d4161d3ce7543a9104e53b8f6d85bdd5a00016a39623740a4c902caf991ef3

69ae3e5bf814388d9f1abe15c9893e7533ba2e64d37f36272140b1b035d1be73

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-05135RLUA-2026-06297

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks kreactjs-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