Malicious Code Injection in nokire-loklok22: A Threat to npm Packages
Summary
MAL-2025-162874: Malicious code in nokire-loklok22 (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-loklok22' is part of the npm ecosystem, which is widely used for JavaScript package management. It 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 that manipulate package metadata and publish numerous variants to inflate developer reputation scores.
Vulnerability Detail
The vulnerability in 'nokire-loklok22' 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 pollution of the npm registry. The ramifications of this vulnerability include potential security risks for developers who unknowingly use these packages, as well as damage to the integrity of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-loklok22If 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, avoid using the 'nokire-loklok22' package and consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The 'nokire-loklok22' package poses a significant threat due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain the integrity of their applications.
See every vulnerability recorded for nokire-loklok22 →
FAQ
The main issue is that it contains malicious code that modifies package metadata and floods the npm registry with derivative packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.
You should uninstall the package immediately using 'npm uninstall nokire-loklok22' and check for any other affected packages.
Yes, consider using other npm packages that provide similar functionality but do not have known vulnerabilities.
This vulnerability can lead to a loss of trust in the npm ecosystem as it allows malicious actors to manipulate package metadata and publish harmful variants.
