Malicious Code Injection in kamasada-nutsai-aasaffa: A Threat to npm Packages
Summary
MAL-2025-157364: Malicious code in kamasada-nutsai-aasaffa (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 kamasada-nutsai-aasaffa package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development and distribution of JavaScript applications. However, it has been identified as part of a malicious campaign that aims to exploit npm's publishing capabilities, leading to potential security risks for developers and their applications.
Vulnerability Detail
The vulnerability stems from the package's involvement in a token reward campaign that floods the npm registry with derivative packages. These packages contain scripts designed to automatically modify the package.json file, removing private flags and changing version numbers. The malicious payload generates random package names and continuously republishes variants, polluting the npm registry and potentially compromising the integrity of other packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall kamasada-nutsai-aasaffa
If 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 measure, you can avoid using the kamasada-nutsai-aasaffa package and monitor your package-lock.json file for any unauthorized changes. Additionally, consider using tools like Vulert to monitor your dependencies for vulnerabilities.
Conclusion
The kamasada-nutsai-aasaffa package poses a significant security risk due to its malicious code that modifies package configurations and floods the npm registry. Developers should take immediate action to remove this package and utilize tools like Vulert to monitor their projects for vulnerabilities.
See every vulnerability recorded for kamasada-nutsai-aasaffa →
FAQ
It is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.
The vulnerability can lead to unauthorized modifications in your package.json file and the proliferation of malicious packages in your project.
You should remove the kamasada-nutsai-aasaffa package immediately and monitor your project for any unusual activity.
Yes, Vulert allows you to monitor your package-lock.json file for vulnerabilities in real-time without requiring code access or installation.
Regularly audit your dependencies, use tools like Vulert for monitoring, and stay updated on security advisories related to the packages you use.