Which versions of fatfingers-vroooom are malicious?

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

How do I remediate fatfingers-vroooom if I installed it?

Remove fatfingers-vroooom from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed fatfingers-vroooom — how do I know if it already compromised me?

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

Yes — fatfingers-vroooom is associated with the GHSA-6rrv-rg7x-p6vh 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 fatfingers-vroooom 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 fatfingers-vroooom (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 fatfingers-vroooom across your stack and pipelines.

Malicious package

fatfingers-vroooomnpm

fatfingers-vroooom is a confirmed malicious npm package (MAL-2025-3964) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in fatfingers-vroooom (npm)

MAL-2025-3964

Immediate action

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

npm uninstall fatfingers-vroooom

What this malware does

The package communicates with a domain associated with malicious activity.

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)

70269dfcd84329c54e31c615cd257ee10ba9b7d258641d1c0b17b4621744ceed

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for fatfingers-vroooom (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 fatfingers-vroooom across your stack and pipelines.
If you installed it — respond
Remove fatfingers-vroooom from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If fatfingers-vroooom 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 fatfingers-vroooom 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. fatfingers-vroooom 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-6rrv-rg7x-p6vh

References

github.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks fatfingers-vroooom-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database