Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

fuels-versionsnpm

Advisory published Updated

fuels-versions is a confirmed malicious npm package (MAL-2026-15673) 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-versions (npm)

MAL-2026-15673
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall fuels-versions

What this malware does

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

bin/cli.js contains a hardcoded out-of-band callback URL at https://oobme.kunalsharma0553.workers.dev/r/7bq6fz3l15r9 and, on execution, collects the installer's username (os.userInfo() / whoami), os.hostname(), and os.platform() and POSTs them to that endpoint. The package name resembles the Fuel Labs ecosystem and has the shape of a dependency-confusion / typosquat probe that beacons host identity when the CLI is run (e.g., via npx or as an installed bin).

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)

c5d918cf489cad4b651a43b1d1b2b64d91e7194c593782b23297041e3c68cb37
35d9f8a553c586813518fefc4735aa6ee3416720489a27c83b8eff10c1a6a755

Detection & response playbook

Backdoor / remote access
  1. Find it

    Search your lockfiles and build artifacts for fuels-versions (version 1.0.0).

  2. If you installed it — respond

    fuels-versions 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.

  3. Did it already run?

    If fuels-versions 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

No. fuels-versions 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

GHSA-7478-v9hq-9835IN-MAL-2026-019396

References

Credits

  • Amazon Inspector · finder
  • Cyberstorm.mu team · finder

Detect & block this

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

Explore

fuels-versions (npm) malicious package — MAL-2026-15673 | O3 Security