Malicious Code Injection in gracesmith Package: npm Vulnerability Overview
Summary
MAL-2025-171275: Malicious code in gracesmith (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 gracesmith package is a Node.js library available on npm, primarily used for various development tasks within JavaScript applications. However, it has been identified as part of a malicious campaign that exploits npm's package publishing system. This vulnerability allows attackers to manipulate the package's metadata and publish harmful derivatives, potentially compromising the integrity of applications that rely on it.
Vulnerability Detail
The vulnerability originates from the gracesmith package being associated with the tea.xyz token reward campaign, which floods npm with malicious packages. These packages contain scripts that automatically modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior leads to the pollution of the npm registry and can inflate developer reputation scores fraudulently, posing risks to users and developers alike.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall gracesmithIf 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 remove the gracesmith package from your project by executing 'npm uninstall gracesmith'. This action will prevent any potential exploitation until a secure version is available.
Conclusion
The gracesmith package has been identified as a vector for malicious code injection, posing significant risks to applications that utilize it. It is essential for developers to take immediate action by updating or removing the package and to monitor their dependencies for vulnerabilities using tools like Vulert.
See every vulnerability recorded for gracesmith →
FAQ
gracesmith is a Node.js package used for various development tasks, but it has been compromised and is now associated with malicious activities.
The vulnerability can lead to the injection of malicious code into your application, potentially compromising its security and integrity.
You should immediately update or uninstall the gracesmith package to protect your application from potential threats.
You can use Vulert, which monitors your package-lock.json file for vulnerabilities in real-time without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
