Malicious Code Injection in kapa-safa-agada: A Threat to npm Ecosystem
Summary
MAL-2025-157398: Malicious code in kapa-safa-agada (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
kapa-safa-agada is an npm package that has been identified as part of a malicious campaign targeting the npm ecosystem. This package is associated with the tea.xyz token reward initiative, which has been known to flood the npm registry with derivative packages. The primary functionality of this package is to serve as a tool for developers, but it has been compromised to include harmful scripts that manipulate package metadata.
Vulnerability Detail
The vulnerability in kapa-safa-agada stems from its inclusion in a malicious campaign that generates and publishes derivative packages with altered metadata. The malicious code modifies the package.json file by removing private flags, changing version numbers, and creating random package names. This behavior not only inflates developer reputation scores for token rewards but also pollutes the npm registry, potentially leading to security risks for users who unknowingly install these compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall kapa-safa-agadaIf 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 kapa-safa-agada package and look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity and reputation of packages before installation.
Conclusion
The kapa-safa-agada package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to be vigilant, regularly update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, developers can protect their projects from potential threats.
See every vulnerability recorded for kapa-safa-agada →
FAQ
kapa-safa-agada is an npm package that has been compromised to include malicious code as part of a broader campaign targeting the npm ecosystem.
If you have installed kapa-safa-agada, your project may be at risk of having its package metadata altered, leading to potential security vulnerabilities and reputation damage.
You can use Vulert to monitor and alert for open-source vulnerabilities in your software. By simply uploading your package-lock.json file, you can check for any vulnerabilities, including those related to kapa-safa-agada.
If you find the kapa-safa-agada package in your project, uninstall it immediately and replace it with a secure alternative. Regularly update your dependencies to mitigate risks.
To prevent similar vulnerabilities, always review package dependencies, use tools like Vulert for real-time monitoring, and stay informed about security advisories related to the packages you use.
