Malicious Code Injection in nokire-sekiya40: A Threat to npm Ecosystem
Summary
MAL-2025-163430: Malicious code in nokire-sekiya40 (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-sekiya40' is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing numerous derivative packages with randomized names. This behavior not only clutters the npm registry but also poses significant security risks to developers using these packages.
Vulnerability Detail
The vulnerability in 'nokire-sekiya40' originates from its malicious code, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This leads to the continuous republishing of variants that pollute the npm registry. The ramifications include potential exposure of sensitive data, compromised developer environments, and a general degradation of trust in the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-sekiya40If 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 prevent the installation of this package by using npm's package-lock.json to lock your dependencies. Additionally, you can monitor your project for vulnerabilities using Vulert, which analyzes your package-lock.json to alert you in real-time about any open-source vulnerabilities.
Conclusion
The 'nokire-sekiya40' package poses a significant threat to the npm ecosystem due to its malicious code that modifies package files and repopulates the registry with harmful variants. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities using tools like Vulert.
See every vulnerability recorded for nokire-sekiya40 →
FAQ
'nokire-sekiya40' is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the automatic generation of derivative packages.
The vulnerability can lead to the exposure of sensitive data and compromise the integrity of your development environment, as well as contribute to the pollution of the npm registry.
You should remove the package from your project immediately and monitor for any updates or patches that may be released.
Yes, Vulert can monitor your package-lock.json for vulnerabilities like this one and alert you in real-time without requiring code access or installation.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
