Malicious Code Injection in nokire-lokcek91: A Threat to npm Packages
Summary
MAL-2025-162850: Malicious code in nokire-lokcek91 (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-lokcek91' 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. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores, posing a significant risk to developers and users alike.
Vulnerability Detail
The vulnerability in 'nokire-lokcek91' originates from its design as part of a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can compromise the integrity of the software supply chain. The malicious payload can potentially allow unauthorized access to sensitive information and disrupt the normal functioning of applications relying on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-lokcek91If 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-lokcek91' package from your project by executing the command: 'npm uninstall nokire-lokcek91'. This will prevent the malicious code from executing until a secure version is available.
Conclusion
The 'nokire-lokcek91' package poses a significant risk due to its malicious code designed to manipulate npm package metadata. It is crucial for developers to take immediate action by updating or removing the package to safeguard their applications. Utilizing tools like Vulert can help in monitoring vulnerabilities effectively.
See every vulnerability recorded for nokire-lokcek91 →
FAQ
The vulnerability can lead to unauthorized modifications of your package metadata, potentially exposing sensitive information and affecting the integrity of your applications.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By using the Vulert playground at Vulert Scanner, you can check your application without any signup.
If an immediate update is not possible, consider removing the package from your project as a temporary measure to mitigate risks.
While specific exploits have not been detailed, the nature of the vulnerability suggests that it can be leveraged to manipulate package integrity and developer reputation.
Regularly audit your dependencies, use tools like Vulert for monitoring, and stay updated with security advisories related to the packages you use.
