Malicious Code Injection in nokire-sekiya44: A Threat to npm Ecosystem
Summary
MAL-2025-163434: Malicious code in nokire-sekiya44 (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-sekiya44' is part of the npm ecosystem, which is a popular package manager for JavaScript. It is often used to manage dependencies in web applications. However, this package has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the generation and publication of derivative packages. The malicious nature of this package compromises the integrity of the npm registry and poses risks to developers and users relying on it.
Vulnerability Detail
The vulnerability in 'nokire-sekiya44' originates from its association with the tea.xyz token reward campaign. It contains scripts that automatically modify the package.json file to remove private flags, alter version numbers, and generate random package names. This leads to the continuous republishing of variants that pollute the npm registry, potentially affecting other packages and developers by inflating reputation scores fraudulently. The malicious payload can also lead to unintentional exposure of sensitive data if private flags are removed.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-sekiya44If 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-sekiya44' 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. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The 'nokire-sekiya44' package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package integrity and developer reputation. It is crucial for developers to be vigilant and remove such packages from their projects to maintain security and integrity.
See every vulnerability recorded for nokire-sekiya44 →
FAQ
'nokire-sekiya44' is an npm package that has been identified as malicious and is part of a campaign to inflate developer reputation scores.
The vulnerability can lead to the exposure of sensitive data and the pollution of the npm registry, affecting the integrity of your project's dependencies.
You should uninstall 'nokire-sekiya44' immediately using 'npm uninstall nokire-sekiya44' and check for alternative packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
