Malicious Code Injection in nokire-nana42: A Threat to npm Users
Summary
MAL-2025-163196: Malicious code in nokire-nana42 (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-nana42' is part of a series of npm packages that have been linked to a token reward campaign by tea.xyz. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The malicious nature of this package poses significant risks to users and the integrity of the npm registry.
Vulnerability Detail
The vulnerability in 'nokire-nana42' originates from its design to include autopublish scripts that modify the package.json file. This modification removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants. This behavior not only pollutes the npm registry but also compromises the security and reliability of applications that depend on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-nana42If 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 'nokire-nana42' package from your project by executing the command: 'npm uninstall nokire-nana42'. This will prevent any malicious code from executing while you seek a secure alternative.
Conclusion
The 'nokire-nana42' package poses a significant threat due to its malicious code that alters package metadata and republish behavior. Users are advised to update or remove the package to safeguard their applications. Utilizing tools like Vulert can help in monitoring and managing open-source vulnerabilities effectively.
See every vulnerability recorded for nokire-nana42 →
FAQ
The main issue is that it contains malicious code that modifies package.json and republish variants, which can compromise the security of applications.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit the Vulert playground at Vulert Scanner to check your application without any signup.
If you cannot update the package right away, consider uninstalling it as a temporary measure to mitigate the risk of exploitation.
While specific exploits have not been detailed, the behavior of the package suggests that it can lead to reputation inflation and potential misuse of the npm registry.
Regularly audit your dependencies, use tools like Vulert for monitoring, and stay informed about vulnerabilities in the packages you use.
