Malicious Code Injection in nokire-sekiya99: A Threat to npm Users
Summary
MAL-2025-163494: Malicious code in nokire-sekiya99 (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-sekiya99' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to manipulate developer reputation scores by automatically generating and publishing derivative packages with randomized names. Its functionality is primarily centered around automating the publishing process, which unfortunately opens the door to malicious activities.
Vulnerability Detail
The vulnerability in 'nokire-sekiya99' stems from its malicious payload that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to pollute the npm registry by continuously republishing variants, which can lead to a compromised development environment and potential security risks for users relying on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-sekiya99If 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-sekiya99' package from your project by executing 'npm uninstall nokire-sekiya99'. This will prevent any malicious code from executing while you seek a secure alternative.
Conclusion
The 'nokire-sekiya99' package poses a significant threat due to its malicious code that alters package metadata and floods the npm registry. Users are advised to update or remove the package to mitigate risks. Utilizing tools like Vulert can help in monitoring and identifying vulnerabilities in open-source dependencies.
See every vulnerability recorded for nokire-sekiya99 →
FAQ
The main issue is that it contains malicious code that modifies package.json and floods the npm registry with derivative packages.
You can use Vulert, which monitors open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.
Using this package can lead to a polluted npm registry, compromised developer reputation, and potential security vulnerabilities in your application.
Regularly audit your dependencies, use tools like Vulert for monitoring, and stay updated on security advisories related to your packages.
If no patched version is available, consider removing the package and looking for alternative solutions that provide similar functionality without the associated risks.
