Malicious Code Injection in nokire-sekiya26: A Threat to npm Packages
Summary
MAL-2025-163414: Malicious code in nokire-sekiya26 (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-sekiya26' is part of the npm ecosystem, which is widely used for JavaScript package management. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. This specific package is designed to manipulate its own metadata and publish variants to inflate developer reputation scores, posing a significant risk to users and the integrity of the npm registry.
Vulnerability Detail
The vulnerability in 'nokire-sekiya26' originates from its malicious design, which includes 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 that can pollute the npm registry, potentially compromising other packages and affecting developers' reputations. The malicious payload can also allow unauthorized access to sensitive data if integrated into a project.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-sekiya26If 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
Currently, there are no specific workarounds to neutralize the effects of this malicious package. The best approach is to avoid using 'nokire-sekiya26' and monitor your dependencies for any signs of compromise.
Conclusion
The 'nokire-sekiya26' package poses a serious threat due to its malicious code designed to manipulate package metadata and publish variants. It is crucial to remove this package from your projects and monitor your dependencies for any signs of compromise. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for nokire-sekiya26 →
FAQ
'nokire-sekiya26' is an npm package that has been identified as malicious, designed to manipulate package metadata and publish variants to inflate developer reputation scores.
The vulnerability can lead to unauthorized modifications in your project's dependencies, potentially compromising security and integrity.
You should immediately uninstall 'nokire-sekiya26' from your project using the command: npm uninstall nokire-sekiya26.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. You can check your application for vulnerabilities without signup at the Vulert playground.
Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay updated on known vulnerabilities in the npm ecosystem.
