Malicious Code Injection in teagood-lokika74: A Threat to npm Ecosystem

teagood-lokika74 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-166942: Malicious code in teagood-lokika74 (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

teagood-lokika74 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to interact with the npm registry, potentially inflating developer reputation scores through automated publishing. However, it has been identified as containing malicious code that can compromise the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in teagood-lokika74 originates from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the automatic generation and publication of derivative packages, polluting the npm registry and potentially harming developers' reputations and the integrity of the ecosystem.

How To Fix

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

npm uninstall teagood-lokika74

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 workaround, you can avoid using the teagood-lokika74 package altogether and consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The discovery of malicious code in the teagood-lokika74 package poses a significant threat to the npm ecosystem. It is crucial for developers to take immediate action by removing the affected package and monitoring their projects for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for teagood-lokika74 →

Share this vulnerability

FAQ

teagood-lokika74 is an npm package involved in the tea.xyz token reward campaign, which has been identified as containing malicious code.

The malicious code modifies your package.json file and can lead to the automatic publication of derivative packages, potentially harming your project's reputation.

You should uninstall the package immediately using 'npm uninstall teagood-lokika74' and check for any other affected packages.

Yes, you can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file.

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

How To Fix

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

npm uninstall teagood-lokika74

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