Malicious Code Injection in teagood-lokika75: A Threat to npm Users

teagood-lokika75 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-166943: Malicious code in teagood-lokika75 (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

teagood-lokika75 is an npm package that appears to be part of a larger campaign associated with the tea.xyz token reward system. This package, like others in the campaign, is designed to manipulate the npm registry by generating and publishing numerous derivative packages with randomized names. The primary function of these packages is to inflate developer reputation scores for token rewards, which can lead to significant pollution of the npm ecosystem.

Vulnerability Detail

The vulnerability in teagood-lokika75 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 the npm registry. This behavior not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly incorporate these malicious packages into their projects.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall teagood-lokika75

If 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 teagood-lokika75 package and instead look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities in real-time.

Conclusion

The discovery of malicious code in the teagood-lokika75 npm package highlights the importance of vigilance when managing dependencies in software projects. By understanding the nature of this vulnerability and taking proactive steps to mitigate risks, developers can protect their applications and maintain the integrity of the npm ecosystem.

See every vulnerability recorded for teagood-lokika75 →

Share this vulnerability

FAQ

teagood-lokika75 is an npm package involved in a campaign to inflate developer reputation scores for token rewards, often containing malicious code.

The malicious code modifies your package.json file, removes private flags, and can lead to the pollution of the npm registry with unwanted packages.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

If you have installed teagood-lokika75, you should uninstall it immediately using 'npm uninstall teagood-lokika75' and look for safer alternatives.

Yes, regularly monitor your dependencies using tools like Vulert, which can alert you in real-time about open-source vulnerabilities in your software.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall teagood-lokika75

If 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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback