Malicious Code Injection in nokire-sekiya52: A Threat to npm Packages
Summary
MAL-2025-163443: Malicious code in nokire-sekiya52 (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-sekiya52' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises its integrity and the integrity of the npm registry.
Vulnerability Detail
The vulnerability in 'nokire-sekiya52' originates from its malicious payload, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to a significant increase in the number of low-quality or malicious packages, potentially affecting developers who rely on the npm ecosystem for legitimate packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-sekiya52If 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-sekiya52' package and look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity and reputation of packages before including them in your project.
Conclusion
The 'nokire-sekiya52' package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry with harmful variants. It is essential to remove this package from your projects and monitor your dependencies for vulnerabilities to maintain the integrity of your software.
See every vulnerability recorded for nokire-sekiya52 →
FAQ
The 'nokire-sekiya52' package is an npm package linked to a token reward campaign that has been identified as containing malicious code.
The malicious code modifies your package.json file and can lead to the proliferation of low-quality or harmful packages in the npm registry, potentially compromising your project's security.
You should uninstall the package immediately using 'npm uninstall nokire-sekiya52' and check your project for any other vulnerable packages.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time, allowing you to stay informed about potential threats.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
