Malicious Code Injection in nokire-loklok52: A Threat to npm Users
Summary
MAL-2025-162907: Malicious code in nokire-loklok52 (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-loklok52 is part of a series of malicious packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by automatically generating and publishing derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for token rewards, making it a significant concern for developers relying on npm for package management.
Vulnerability Detail
The vulnerability in nokire-loklok52 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 not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these packages, leading to potential security breaches and loss of reputation.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-loklok52If 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-loklok52 package and replace it with a trusted alternative. Always verify the integrity and source of packages before including them in your project.
Conclusion
The nokire-loklok52 package poses a significant threat to the npm ecosystem due to its malicious behavior. Developers are advised to remove this package from their projects and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can enhance your security posture by providing real-time alerts for open-source vulnerabilities.
See every vulnerability recorded for nokire-loklok52 →
FAQ
Nokire-loklok52 is an npm package that has been identified as malicious, designed to manipulate the npm registry for token rewards.
Using the nokire-loklok52 package can compromise your project's integrity, lead to security breaches, and negatively impact your developer reputation.
You should uninstall the package immediately using the command 'npm uninstall nokire-loklok52' and check your project for any other affected dependencies.
You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities. You can check your application for vulnerabilities without signing up at the Vulert playground.
Yes, consider using well-known and trusted packages that serve similar functionalities without the associated risks.
