Malicious Code Injection in nokire-sekiya10: A Threat to npm Ecosystem
Summary
MAL-2025-163396: Malicious code in nokire-sekiya10 (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-sekiya10' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. Its primary function is to manipulate package metadata and publish derivative packages, potentially harming developers' reputations and polluting the npm registry.
Vulnerability Detail
The vulnerability in 'nokire-sekiya10' originates from its design to include malicious scripts that modify the package.json file. This includes removing private flags, altering version numbers, and generating random package names, which can lead to the automatic publication of numerous derivative packages. The ramifications of this vulnerability include the potential for developers to unknowingly publish compromised packages, leading to reputational damage and security risks within the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-sekiya10If 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-sekiya10' package from your project by executing the command: 'npm uninstall nokire-sekiya10'. This will prevent any malicious code from executing until a secure version is available.
Conclusion
The 'nokire-sekiya10' package poses a significant risk due to its malicious code that alters package metadata and publishes unauthorized derivatives. It is crucial for developers to take immediate action by updating or removing the package to safeguard their projects and maintain the integrity of the npm ecosystem.
See every vulnerability recorded for nokire-sekiya10 →
FAQ
'nokire-sekiya10' is an npm package that has been identified as containing malicious code aimed at manipulating package metadata.
This vulnerability can lead to the automatic publication of malicious packages, potentially harming your project's reputation and security.
You should uninstall the package immediately and check for any updates or patches that may address the vulnerability.
You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
