Malicious Code Vulnerability in nokire-nakala69: A Threat to npm Ecosystem
Summary
MAL-2025-163024: Malicious code in nokire-nakala69 (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 nokire-nakala69 is part of the npm ecosystem and appears to be involved in a token reward campaign for the tea.xyz protocol. This package is designed to manipulate the npm registry by generating and publishing numerous derivative packages with randomized names, aimed at inflating developer reputation scores. It is crucial for developers to be aware of such malicious packages that can compromise the integrity of their applications.
Vulnerability Detail
The vulnerability originates from the malicious code embedded in the nokire-nakala69 package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names, which leads to the continuous republishing of these variants. The ramifications include pollution of the npm registry, potential security risks for applications that depend on these packages, and a compromised developer reputation system. The malicious payload is particularly concerning as it can affect the integrity of applications relying on npm packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-nakala69If 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 nokire-nakala69 package and monitor your dependencies for any malicious activity. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The nokire-nakala69 package poses a significant threat to the npm ecosystem due to its malicious code that modifies package configurations and repopulates the registry with harmful variants. Developers are urged to take immediate action to remove this package and utilize monitoring tools like Vulert to safeguard their applications from potential vulnerabilities.
See every vulnerability recorded for nokire-nakala69 →
FAQ
Nokire-nakala69 is an npm package that has been identified as containing malicious code aimed at manipulating the npm registry.
The malicious code can modify your package.json, remove private flags, and republish variants, potentially compromising your application's integrity.
You should remove the nokire-nakala69 package from your project and monitor your dependencies for any further vulnerabilities.
Regularly update your dependencies, use tools like Vulert to monitor vulnerabilities, and review packages before installation.
Yes, you can use Vulert's playground at Vulert Scanner to check your application for vulnerabilities without requiring any installation.
