Malicious Code Injection in nokire-sekiya33: A Threat to npm Ecosystem
Summary
MAL-2025-163422: Malicious code in nokire-sekiya33 (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-sekiya33' is part of a larger set of malicious packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate the npm ecosystem by creating and publishing numerous derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for token rewards, posing a significant risk to the integrity of the npm registry.
Vulnerability Detail
The vulnerability in 'nokire-sekiya33' originates from its malicious code that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, which leads to the continuous republishing of these variants. This not only pollutes the npm registry but also compromises the security of applications relying on these packages, potentially allowing for further exploitation and misuse.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-sekiya33If 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-sekiya33' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities.
Conclusion
The 'nokire-sekiya33' package poses a significant threat to the npm ecosystem due to its malicious behavior. It is crucial for developers to be aware of such vulnerabilities and take immediate action to protect their applications. Utilizing tools like Vulert can aid in identifying and managing these risks effectively.
See every vulnerability recorded for nokire-sekiya33 →
FAQ
The main risk is that it modifies package.json files and republish variants, which can lead to security vulnerabilities in applications that depend on it.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
You should uninstall the package immediately using 'npm uninstall nokire-sekiya33' and monitor for any updates or patches.
Yes, consider searching for other npm packages that offer similar functionality but do not have known vulnerabilities.
Vulert monitors your package-lock.json file to alert you in real-time about open-source vulnerabilities in your software, helping you maintain security.
