Malicious Code Injection in teagood-lokika1 Package - npm Vulnerability

teagood-lokika1 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-166870: Malicious code in teagood-lokika1 (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The teagood-lokika1 package is part of the tea.xyz token reward campaign, which has been known to flood the npm ecosystem with malicious packages. These packages are designed to manipulate developer reputation scores through automated publishing scripts. The vulnerability in this package allows for the modification of critical files, leading to potential exploitation and pollution of the npm registry.

Vulnerability Detail

The vulnerability originates from the presence of malicious code within the teagood-lokika1 package. This code is designed to remove private flags from the package.json file, alter version numbers, and generate random package names, which can lead to the proliferation of derivative packages. The ramifications include the potential for developers to unknowingly publish compromised packages, thereby damaging their reputation and contributing to the pollution of the npm ecosystem.

How To Fix

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

npm uninstall teagood-lokika1

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-lokika1 package and monitor your dependencies for any signs of malicious activity. Additionally, consider using tools like Vulert to scan your package-lock.json for vulnerabilities. You can access the Vulert playground at https://vulert.com/scanner to check if your application is affected by this vulnerability without needing to sign up.

Conclusion

The teagood-lokika1 package poses a significant risk due to its malicious code designed to manipulate npm packages. It is crucial to remove this package from your project and monitor your dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for teagood-lokika1 →

Share this vulnerability

FAQ

teagood-lokika1 is an npm package associated with the tea.xyz token reward campaign, which has been identified as containing malicious code.

The malicious code can modify your package.json file, remove private flags, and publish derivative packages, potentially harming your project's integrity and reputation.

You should remove the teagood-lokika1 package from your project immediately and check for any other compromised packages.

You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time. Visit https://vulert.com for more information.

Regularly update your dependencies, use reputable sources for packages, and employ vulnerability scanning tools to identify potential risks.

How To Fix

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

npm uninstall teagood-lokika1

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