Which versions of hyper-fullfacing are malicious?

The following npm versions of hyper-fullfacing are flagged malicious: 1.0.3. Treat any of these as compromised.

How do I remediate hyper-fullfacing if I installed it?

hyper-fullfacing 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.

I already installed hyper-fullfacing — how do I know if it already compromised me?

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

Yes — hyper-fullfacing is associated with the GHSA-mv92-7x3f-qm3c 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 hyper-fullfacing 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 hyper-fullfacing (version 1.0.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging hyper-fullfacing across your stack and pipelines.

Malicious package

hyper-fullfacingnpm

Malicious code in hyper-fullfacing (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191397

Immediate action

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

npm uninstall hyper-fullfacing

What this malware does

The package hyper-fullfacing was found to contain malicious code.

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.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

1 flagged

1.0.3

Indicators of compromise (SHA-256)

858f411bf591fc6a429c23874a58ecd8c39b2a975343f0514cbacc82b2c3307f

a9c05ea2ff38a274ac4ddcadb9206e1f6d6736e32ce536e149160e99fdd37ba7

0068679876dedee5d5fc8affa29f353019af199cd3a22493bc1e122f440b32bc

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for hyper-fullfacing (version 1.0.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging hyper-fullfacing across your stack and pipelines.
If you installed it — respond
hyper-fullfacing 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.
Did it already run?
If hyper-fullfacing 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 hyper-fullfacing 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. hyper-fullfacing on npm has been identified as a malicious package (version 1.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-mv92-7x3f-qm3c

References

Credits

Amazon Inspector · finder

Detect & block this

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

Malware detection Runtime egress monitoring