Malicious Code Injection in teagood-lokika49: A Threat to npm Packages

teagood-lokika49 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-166914: Malicious code in teagood-lokika49 (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

teagood-lokika49 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to interact with the npm ecosystem, primarily for developers looking to enhance their reputation through token rewards. However, it has been identified as containing malicious scripts that can compromise the integrity of the npm registry and the applications relying on it.

Vulnerability Detail

The vulnerability in teagood-lokika49 originates from its inclusion in a campaign that floods npm with derivative packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which can lead to a polluted npm registry. This behavior not only affects the reputation of developers but also poses a risk of dependency confusion and potential security breaches in applications that utilize these packages.

How To Fix

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

npm uninstall teagood-lokika49

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 affected package by replacing it with a trusted alternative or by manually auditing your package-lock.json file to ensure that no malicious packages are included.

Conclusion

The discovery of malicious code in teagood-lokika49 highlights the importance of vigilance in managing npm packages. By understanding the nature of this vulnerability and taking proactive steps to mitigate its impact, developers can protect their applications and maintain the integrity of the npm ecosystem.

See every vulnerability recorded for teagood-lokika49 →

Share this vulnerability

FAQ

teagood-lokika49 is an npm package associated with the tea.xyz token reward campaign, which has been identified to contain malicious code.

The vulnerability can lead to the injection of malicious code into your application, potentially compromising its security and integrity.

You should uninstall the package immediately using 'npm uninstall teagood-lokika49' and audit your dependencies for any other malicious packages.

You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access or installation.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

npm uninstall teagood-lokika49

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