Malicious Code Injection in nokire-nakala87: A Threat to npm Ecosystem
Summary
MAL-2025-163044: Malicious code in nokire-nakala87 (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-nakala87' is part of the npm ecosystem, which is widely used for JavaScript package management. This package was identified as part of a malicious campaign that aimed to exploit the npm registry by flooding it with derivative packages. These packages typically include scripts that automatically generate and publish new packages with altered names and metadata, thereby inflating developer reputation scores for token rewards.
Vulnerability Detail
The vulnerability in 'nokire-nakala87' originates from its inclusion in a malicious campaign associated with the tea.xyz token reward initiative. The package contains scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can compromise the integrity of the ecosystem. The malicious payload can potentially allow unauthorized access to sensitive data or lead to the installation of compromised packages by unsuspecting developers.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-nakala87If 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-nakala87' package and instead utilize alternative packages that provide similar functionality without the associated risks. Additionally, consider implementing strict package auditing practices to monitor for any malicious packages in your dependencies.
Conclusion
The 'nokire-nakala87' package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package metadata and flood the registry. It is crucial for developers to remove this package from their projects and adopt best practices for dependency management to safeguard their applications.
See every vulnerability recorded for nokire-nakala87 →
FAQ
The main issue is that it contains malicious code designed to manipulate package metadata and flood the npm registry with derivative packages.
You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities in real-time. You can also check your application using the Vulert playground at Vulert Scanner without any signup.
If you have installed the package, you should uninstall it immediately using 'npm uninstall nokire-nakala87' and review your dependencies for any other potential threats.
While specific exploits have not been detailed, the malicious behavior of the package can lead to unauthorized access and compromise the integrity of the npm ecosystem.
To prevent similar vulnerabilities, regularly audit your dependencies, use trusted sources for packages, and consider implementing automated tools that monitor for vulnerabilities.
