fuels-typegennpm
Advisory published Updated
fuels-typegen is a confirmed malicious npm package (MAL-2026-15593) 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-typegen (npm)
What this malware does
The package name resembles the legitimate @fuel-ts/typegen. On execution of the CLI in bin/cli.js, the code collects the local username (whoami / os.userInfo), os.hostname(), platform, and package name and POSTs them as JSON to the hardcoded endpoint https://oobme.kunalsharma0553.workers.dev/r/7bq6fz3l15r9. The manifest's own description states the package's purpose is to POST identifiers to an out-of-band callback, and the bin name (hyperliquid-composer) is unrelated to the package name, consistent with dependency-confusion or typosquat delivery.
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-typegen' @ 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-typegen (version 1.0.0).
If you installed it — respond
fuels-typegen is a typosquat — you almost certainly intended a legitimately-named package. Remove fuels-typegen, 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-typegen 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-typegen-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.