Which versions of hreactjs are malicious?

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

How do I remediate hreactjs if I installed it?

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

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

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

Search your lockfiles and build artifacts for hreactjs (4 malicious versions).

Malicious package

hreactjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

Malicious code in hreactjs (npm)

MAL-2026-7295

Immediate action

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

npm uninstall hreactjs

Malicious versions

4 flagged

1.1.11.1.21.1.48.7.6

Indicators of compromise (SHA-256)

4c266e71f2c8a394c002edbb3c8c98b0391fc87415209c3b0f46f3e137439491

42fe4685b30f03e359acc18a63c53e959bcdf76197b7a82f9f007941ca99789a

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for hreactjs (4 malicious versions).
If you installed it — respond
Remove hreactjs 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 hreactjs 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. hreactjs on npm has been identified as a malicious package (versions 1.1.1, 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-05109RLUA-2026-06273

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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