Malicious Code Injection in nokire-loklok32: A Threat to npm Ecosystem
Summary
MAL-2025-162885: Malicious code in nokire-loklok32 (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-loklok32 is part of the npm ecosystem, which is widely used for JavaScript package management. It is designed to facilitate the development and sharing of JavaScript code. However, this package has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages with randomized names. This behavior poses a significant risk to the integrity of the npm registry and the security of applications relying on this package.
Vulnerability Detail
The vulnerability in nokire-loklok32 originates from its involvement in the tea.xyz token reward campaign. This campaign utilizes autopublish scripts to modify the package.json file by removing private flags, changing version numbers, and generating random package names. The continuous republishing of these variants pollutes the npm registry, making it difficult for developers to trust the integrity of packages. The malicious payload can lead to unintended consequences, including the introduction of security risks into applications that depend on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-loklok32If 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 workaround, consider using alternative packages that provide similar functionality without the associated risks. Always verify the integrity of packages before including them in your project.
Conclusion
The nokire-loklok32 package presents a significant security risk due to its involvement in a malicious campaign. It is crucial for developers to be aware of this vulnerability and take appropriate actions to secure their applications. By uninstalling the affected package and monitoring for vulnerabilities, developers can help maintain the integrity of their projects.
See every vulnerability recorded for nokire-loklok32 →
FAQ
Nokire-loklok32 is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores.
The vulnerability can introduce malicious code into your application, potentially compromising its security and integrity.
You should uninstall the package immediately using the command: npm uninstall nokire-loklok32.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without requiring any signup.
