Malicious Code Injection in gracgracehillehill: A Threat to npm Users
Summary
MAL-2025-171279: Malicious code in gracgracehillehill (npm). Affected versions are not published. 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
Background
The package 'gracgracehillehill' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to manipulate npm's publishing system, creating numerous derivative packages to inflate developer reputation scores. Its functionality is compromised by malicious scripts that alter package metadata and continuously republish variants, leading to potential security risks for users.
Vulnerability Detail
The vulnerability in 'gracgracehillehill' originates from its association with a malicious campaign that floods the npm registry with derivative packages. The malicious payload modifies the package.json file to remove private flags, changes version numbers, and generates random package names, which can lead to pollution of the npm registry. This behavior not only affects the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall gracgracehillehillIf 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, you can avoid using the 'gracgracehillehill' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities.
Conclusion
The 'gracgracehillehill' package poses a significant risk due to its malicious code that manipulates npm's publishing system. Users are advised to uninstall the package and monitor their projects for vulnerabilities using tools like Vulert. Staying informed and proactive is crucial in maintaining the security of your applications.
See every vulnerability recorded for gracgracehillehill →
FAQ
The main issue is that it contains malicious code that alters package metadata and floods the npm registry with derivative packages.
You can use Vulert's playground at Vulert Scanner to check if your application is affected without needing to sign up.
You should uninstall the package immediately using 'npm uninstall gracgracehillehill' and look for alternatives.
While specific alternatives depend on your use case, consider searching npm for similar packages that do not have known vulnerabilities.
Vulert monitors your package-lock.json file to alert you in real-time about open-source vulnerabilities in your software, ensuring you stay informed.
