Malicious Code Injection in teagood-lokina35: npm Package Vulnerability
Summary
MAL-2025-166999: Malicious code in teagood-lokina35 (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
teagood-lokina35 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which are intended to inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises the integrity of the npm registry.
Vulnerability Detail
The vulnerability in teagood-lokina35 originates from its malicious payload, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants, leading to pollution of the npm registry. This behavior can severely impact developers by inflating reputation scores fraudulently and potentially introducing security risks through unverified packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall teagood-lokina35If 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, you can avoid using the teagood-lokina35 package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your npm packages using tools like npm audit to identify and address vulnerabilities.
Conclusion
The teagood-lokina35 npm package has been identified as containing malicious code that poses a significant risk to developers and the integrity of the npm registry. It is crucial to remove this package from your projects and monitor for similar vulnerabilities using tools like Vulert.
See every vulnerability recorded for teagood-lokina35 →
FAQ
The main issue is that it contains malicious code that modifies package.json files and republishes variants to pollute the npm registry.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
If you have installed teagood-lokina35, you should uninstall it immediately using the command npm uninstall teagood-lokina35.
Yes, you can use tools like Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json.
Using compromised packages can lead to security vulnerabilities, data breaches, and damage to your project's reputation due to the introduction of unverified code.
