Which versions of fuels-forc are malicious?

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

How do I remediate fuels-forc if I installed it?

fuels-forc establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed fuels-forc — how do I know if it already compromised me?

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

Yes — fuels-forc is associated with the IN-MAL-2026-019305, GHSA-h4w6-844f-2fxw 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 fuels-forc 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 fuels-forc (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 fuels-forc across your stack and pipelines.

Malicious package

fuels-forcnpm

fuels-forc is a confirmed malicious npm package (MAL-2026-15626) that opens a backdoor for remote access (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in fuels-forc (npm)

MAL-2026-15626

Immediate action

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

npm uninstall fuels-forc

What this malware does

The package 'fuels-forc' was identified as containing malicious obfuscated code.

bin/cli.js runs whoami and reads os.hostname() / os.platform(), then POSTs the package name together with those host identifiers to the hardcoded endpoint https://oobme.kunalsharma0553.workers.dev/r/7bq6fz3l15r9. The destination is non-first-party and not caller-configurable, and the beacon fires unconditionally on execution. The package name resembles the legitimate Fuel Labs forc toolchain, consistent with a dependency-confusion / typosquat recon lure.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

b993583bec4136d0b060dc6391c10e15f836e605b5b13b97dea6bb7a3dc1e5cd

344f2276052ea5c2599f897c07e58966a228bcfae44ce3ec6409bf6800735374

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for fuels-forc (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 fuels-forc across your stack and pipelines.
If you installed it — respond
fuels-forc establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If fuels-forc 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 fuels-forc 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. fuels-forc 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-019305GHSA-h4w6-844f-2fxw

References

Credits

Amazon Inspector · finder
Cyberstorm.mu team · finder

Detect & block this

O3 blocks fuels-forc-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database