Which versions of raectjs are malicious?

The following npm versions of raectjs are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate raectjs if I installed it?

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

If raectjs was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is raectjs part of a known attack campaign?

Yes — raectjs is associated with the IN-MAL-2026-018255 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 raectjs across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for raectjs (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging raectjs across your stack and pipelines.

Malicious package

raectjsnpm

raectjs is a confirmed malicious npm package (MAL-2026-14187) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in raectjs (npm)

MAL-2026-14187

Immediate action

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

npm uninstall raectjs

What this malware does

scripts/postinstall.js runs on npm install and performs two attacker-beneficial actions. First, it POSTs a JSON platform snapshot to the hardcoded bare-IP endpoint http://193.70.34.101:20099/vote, with the host string reconstructed at runtime by joining ['193','70','34','101'] to evade static hostname matching. Second, it XOR-decodes (key 'stf2026') an embedded byte array (ADDON_ENC) into a URL pointing at a GitHub releases/download/.../main.exe under an attacker-controlled account, fetches the payload into %TEMP%\main.exe, and spawns it detached with stdio:'ignore' and windowsHide:true. On WSL/virtualized Linux it XOR-decodes a PowerShell bridge command and script (BRIDGE_LAUNCHER_ENC, BRIDGE_SCRIPT_PRE_ENC, BRIDGE_SCRIPT_POST_ENC) to invoke the same payload on the Windows host. The fetched binary has no pinning, no hash or signature verification, and the package name uses a cover story ('addon', 'TELEMETRY.addon') while shipping no native source consistent with a real addon (index.js exports {}). Package has no legitimate purpose beyond delivering the dropper.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

f75a611c33224c779330b8d5313702dc44f20d197dd96f62fb236982281b9d09

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for raectjs (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging raectjs across your stack and pipelines.
If you installed it — respond
Remove raectjs 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 raectjs was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks raectjs before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. raectjs on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-018255

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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