Malicious Code Injection in nokire-namiresan52: A Threat to npm Packages
Summary
MAL-2025-163106: Malicious code in nokire-namiresan52 (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-namiresan52' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises the integrity of the npm registry.
Vulnerability Detail
The vulnerability in 'nokire-namiresan52' originates from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially affecting other developers and their projects. The malicious scripts included in this package are designed to automate these harmful actions, making it a significant threat to the integrity of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-namiresan52If 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 'nokire-namiresan52' package altogether. If it is already installed, ensure that your project does not rely on it and remove it immediately. Regularly monitor your package-lock.json file for any unauthorized changes.
Conclusion
The 'nokire-namiresan52' package poses a significant threat due to its malicious code that alters package configurations and republishing behaviors. It is crucial for developers to remove this package from their projects and monitor their dependencies for any unauthorized changes. Utilizing tools like Vulert can help in maintaining the security of your applications.
See every vulnerability recorded for nokire-namiresan52 →
FAQ
The primary risk is the injection of malicious code that modifies package.json files, leading to unauthorized republishing of packages and potential security breaches.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
You should uninstall the package immediately using 'npm uninstall nokire-namiresan52' and check for any dependencies that may be affected.
Currently, there are no known patches for the nokire-namiresan52 package. The best course of action is to remove it from your project.
Vulert monitors and alerts in real-time for open-source vulnerabilities using just the package-lock.json file, allowing you to stay informed about potential threats.
