Which versions of breactjs are malicious?

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

How do I remediate breactjs if I installed it?

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

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

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

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

Malicious package

breactjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

breactjs is a confirmed malicious npm package (MAL-2026-7229) 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 breactjs (npm)

MAL-2026-7229

Immediate action

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

npm uninstall breactjs

Malicious versions

3 flagged

1.1.11.1.48.7.6

Indicators of compromise (SHA-256)

735484e713fb1a4c80788b709963b17170efa355c6b170c8daf39846c2559379

8701f1c33c5e698422351fe7e08cd83e98848f91025315470b6d7d4cd85608a2

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for breactjs (3 malicious versions).
If you installed it — respond
Remove breactjs 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 breactjs 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. breactjs 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-04969RLUA-2026-06100

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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