Which versions of treactjs are malicious?

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

How do I remediate treactjs if I installed it?

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

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

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

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

Malicious package

treactjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7429

Immediate action

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

npm uninstall treactjs

Malicious versions

3 flagged

1.1.21.1.48.7.6

Indicators of compromise (SHA-256)

c3a6341ee9dd0dea458ade9f3f7de40ed1333a72661fc5929c9483314fd29be1

73b55c935849b2e39aff721e964c56af2f754f7ab1bdb19879c206ac1a013013

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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