Malicious Code Injection in nokire-loklok100 Package: A Threat to npm Users
Summary
MAL-2025-162861: Malicious code in nokire-loklok100 (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 nokire-loklok100 package is part of a broader ecosystem within npm, primarily associated with the tea.xyz token reward campaign. This package, like others in the campaign, is designed to manipulate npm's publishing system by generating and publishing numerous derivative packages. Its functionality is compromised due to the presence of malicious scripts that alter package metadata and inflate developer reputation scores, posing a significant risk to users and the integrity of the npm registry.
Vulnerability Detail
The vulnerability in the nokire-loklok100 package stems from its association with malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants that pollute the npm registry. The origin of this vulnerability is linked to a campaign aimed at exploiting npm's publishing mechanisms for token rewards, which can result in reputational damage for developers and potential security risks for users who inadvertently install these compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-loklok100If 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-loklok100 package and any other packages associated with the tea.xyz token reward campaign. Additionally, consider using a tool 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-loklok100 package presents a significant security risk due to its malicious code that alters package metadata and exploits npm's publishing system. 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-loklok100 →
FAQ
The nokire-loklok100 package is an npm package that is part of a malicious campaign aimed at exploiting npm's publishing system for token rewards.
The malicious code modifies your package.json file, removes private flags, and generates random package names, which can lead to security vulnerabilities and reputational damage.
You should uninstall the nokire-loklok100 package immediately using 'npm uninstall nokire-loklok100' and monitor your project for any other vulnerabilities.
Yes, regularly monitor your dependencies using tools like Vulert, which can alert you to open-source vulnerabilities in real-time.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
