NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

@fedfub/utilsnpm

Advisory published Updated

@fedfub/utils is a confirmed malicious npm package (MAL-2026-20291) that steals credentials and exfiltrates sensitive data (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @fedfub/utils (npm)

MAL-2026-20291
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @fedfub/utils

What this malware does

Malicious package. Advertised as "Utility helpers for Node.js", but the postinstall hook runs worm.js (also the package main), a self-propagating credential stealer. On install it collects every environment variable matching KEY/SECRET/TOKEN/PASS/AWS/JWT/STRIPE/PAYPAL/DB_/DATABASE/REDIS/MONGO, up to 5000 characters of every source file under the working directory, and the contents of ~/.ssh, then POSTs them with hostname, username and platform to https://73.218.105.44:8080/collect. It then tries to republish itself under each dependency name of the host project as <name>[email protected] via npm publish, injects itself into package.json files under the home directory, persists with an @reboot crontab entry (or a SYSTEM onlogon scheduled task on Windows), and polls /cmd every 30 seconds, executing whatever command the server returns and posting the output to /result. In a sandboxed install the postinstall connected to 73.218.105.44 and wrote the crontab entry. The package has since been removed from the npm registry. The same author published @fedfub/string-utils with a minified copy of the same code.

Malicious versions

1 flagged
1.0.1

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for @fedfub/utils (version 1.0.1).

  2. If you installed it — respond

    @fedfub/utils 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.

  3. Did it already run?

    If @fedfub/utils 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. @fedfub/utils on npm has been identified as a malicious package (version 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

  • wormsign · finder

Detect & block this

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

Explore

@fedfub/utils (npm) malicious package — MAL-2026-20291 | O3 Security