fuels-corenpm
Advisory published Updated
fuels-core is a confirmed malicious npm package (MAL-2026-15592) that typosquats a legitimate package to trick installs (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in fuels-core (npm)
What this malware does
The package's bin script (bin/cli.js) collects whoami, os.hostname(), and os.platform() and POSTs them along with the package name to a hardcoded Cloudflare Workers URL (https://oobme.kunalsharma0553.workers.dev/r/7bq6fz3l15r9) with no configuration or opt-out. The bin is exposed as generate-schema-viem, and the package name fuels-core resembles the Fuel ecosystem's fuels package, consistent with typosquat/dependency-confusion reconnaissance targeting installers who resolve or invoke this package (e.g., via npx). The package.json description openly states its purpose is to POST package name and whoami to an OOB callback.
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.
The OpenSSF Package Analysis project identified 'fuels-core' @ 1.0.0 (npm) as malicious.
It is considered malicious because:
-
The package communicates with a domain associated with malicious activity.
-
The package executes one or more commands associated with malicious behavior.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
TyposquatFind it
Search your lockfiles and build artifacts for fuels-core (version 1.0.0).
If you installed it — respond
fuels-core is a typosquat — you almost certainly intended a legitimately-named package. Remove fuels-core, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If fuels-core 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
Campaign
References
Credits
- Amazon Inspector · finder
- OpenSSF: Package Analysis · finder
Detect & block this
O3 blocks fuels-core-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.