Critical Security Breach in hyper-fullfacing: Malicious Code Exploitation
Summary
MAL-2025-191397: Malicious code in hyper-fullfacing (npm). Affects hyper-fullfacing versions 1.0.3. No fix is published. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
hyper-fullfacing is an npm package designed for enhancing the functionality of applications built on Node.js. It provides various utilities and features that developers leverage to streamline their development processes. However, this package has recently been compromised, exposing users to significant security risks due to malicious code embedded within its version 1.0.3.
Vulnerability Detail
The vulnerability stems from a compromise by the Sha1-Hulud: The Second Coming NPM worm, which infiltrated the hyper-fullfacing package. This malicious payload is capable of stealing sensitive tokens and credentials, subsequently publishing them to GitHub. Furthermore, the worm can propagate itself to other npm packages owned by the user and establish persistence through GitHub actions. In extreme cases, it may even lead to the destruction of the user's home directory, posing a severe threat to data integrity and security.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall hyper-fullfacingIf it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.
Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →
Workaround
As a temporary workaround, users are advised to remove the hyper-fullfacing package from their projects until a secure version is confirmed. This can be done using the command: npm uninstall hyper-fullfacing. Additionally, monitor your GitHub repositories for any unauthorized changes or actions.
Conclusion
The hyper-fullfacing package has been compromised by a malicious worm, posing serious security threats to users. It is imperative to take immediate action by uninstalling the affected package and monitoring your systems for any unauthorized access. Utilizing tools like Vulert can help in identifying and mitigating such vulnerabilities in the future.
See every vulnerability recorded for hyper-fullfacing →
FAQ
The malicious code is designed to steal sensitive information such as tokens and credentials, and it can also propagate itself to other npm packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.
Immediately uninstall the compromised version using npm uninstall hyper-fullfacing and update to a secure version as soon as it is available.
Yes, the worm can potentially destroy your home directory, leading to significant data loss and system instability.
Regularly monitor your dependencies using tools like Vulert and keep your packages updated to the latest secure versions.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
