Malicious Code Injection in nokire-sekiya20: A Threat to npm Ecosystem
Summary
MAL-2025-163408: Malicious code in nokire-sekiya20 (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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The package 'nokire-sekiya20' is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. These packages are designed to inflate developer reputation scores for token rewards, posing significant risks to developers and users alike.
Vulnerability Detail
The vulnerability in 'nokire-sekiya20' originates from its association with the tea.xyz token reward campaign. It contains malicious scripts that modify the package.json file by removing private flags, altering version numbers, and generating random package names. This 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 and disrupt the normal functioning of applications relying on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-sekiya20If 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-sekiya20' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file for any unauthorized changes.
Conclusion
The 'nokire-sekiya20' package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package metadata and inflate developer reputations. It is essential to remove this package from your projects and monitor for any updates or alternatives to safeguard your applications.
See every vulnerability recorded for nokire-sekiya20 →
FAQ
The primary risk is that it contains malicious code that modifies package.json files, potentially leading to unauthorized access and pollution of the npm registry.
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 immediately uninstall the package using 'npm uninstall nokire-sekiya20' and look for alternatives.
Currently, there are no known patches for the nokire-sekiya20 package, so it is recommended to remove it from your project.
Vulert monitors and alerts in real-time for open-source vulnerabilities using just the package-lock.json file, ensuring that you are informed about any risks associated with your dependencies.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
