Malicious Code Injection in teagood-lokika93: npm Package Vulnerability

teagood-lokika93 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-166963: Malicious code in teagood-lokika93 (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-lokika93 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate token rewards for developers by publishing derivative packages. However, it has been identified as malicious due to its functionality that modifies package metadata and floods the npm registry with unwanted packages.

Vulnerability Detail

The vulnerability in teagood-lokika93 stems from its inclusion in a campaign that uses autopublish scripts to manipulate package.json files. These scripts remove private flags, alter version numbers, and generate random package names, leading to the pollution of the npm registry. This not only affects the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these compromised packages.

How To Fix

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

npm uninstall teagood-lokika93

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, consider using a package-lock.json file to lock down your dependencies and prevent the installation of malicious packages. You can also monitor your dependencies using tools like Vulert, which alerts you to open-source vulnerabilities in real-time without requiring code access or installation.

Conclusion

The teagood-lokika93 package has been identified as a malicious npm package that modifies package metadata and floods the npm registry. It is crucial for developers to remove this package from their projects and monitor their dependencies to maintain the integrity of their applications.

See every vulnerability recorded for teagood-lokika93 →

Share this vulnerability

FAQ

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

The vulnerability can lead to the installation of malicious code that modifies your package.json and floods the npm registry with unwanted packages, potentially compromising your project's integrity.

You should uninstall the package immediately using 'npm uninstall teagood-lokika93' and check for any dependencies that may be affected.

Yes, using a package-lock.json file can help lock down your dependencies. Additionally, using tools like Vulert can provide real-time alerts for open-source vulnerabilities.

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

How To Fix

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

npm uninstall teagood-lokika93

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