Which versions of dreactjs are malicious?

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

How do I remediate dreactjs if I installed it?

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

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

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

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

Malicious package

dreactjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

Malicious code in dreactjs (npm)

MAL-2026-7253

Immediate action

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

npm uninstall dreactjs

Malicious versions

3 flagged

1.1.11.1.48.7.6

Indicators of compromise (SHA-256)

aa05f58ce153278a6fad39148ab0c128fd8d8b934ffc25c1ea8ae0e488effed8

49c97a251e22c21ad9bae91a50a21ac1866ffecd341437615d1e0125e54f7b4d

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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