Which versions of fuel-react are malicious?

The following npm versions of fuel-react are flagged malicious: 91.0.0. Treat any of these as compromised.

How do I remediate fuel-react if I installed it?

fuel-react is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed fuel-react — how do I know if it already compromised me?

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

Yes — fuel-react is associated with the IN-MAL-2026-018511 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 fuel-react 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 fuel-react (version 91.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging fuel-react across your stack and pipelines.

Malicious package

fuel-reactnpm

fuel-react is a confirmed malicious npm package (MAL-2026-14355) that steals credentials and exfiltrates sensitive data (malicious version 91.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in fuel-react (npm)

MAL-2026-14355

Immediate action

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

npm uninstall fuel-react

What this malware does

The package's postinstall.js script executes automatically on npm install and collects host identity plus environment variables (os.hostname(), process.env) and transmits them via an https request. The package name mimics common React tooling but the shipped install-time behavior is host reconnaissance and environment-variable exfiltration, which frequently captures credentials such as npm tokens, CI secrets, and cloud keys present in process.env.

Malicious versions

1 flagged

91.0.0

Indicators of compromise (SHA-256)

8e35f4772b8cba3555519c250662c67395bf57d89feed3feba7ea067b6bb2c27

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for fuel-react (version 91.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging fuel-react across your stack and pipelines.
If you installed it — respond
fuel-react is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If fuel-react 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 fuel-react 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. fuel-react on npm has been identified as a malicious package (version 91.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-018511

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks fuel-react-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database