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

teagood-lokina74 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-167042: Malicious code in teagood-lokina74 (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

teagood-lokina74 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to interact with the npm registry, allowing developers to publish and manage their packages. However, it has been identified as containing malicious code that exploits its functionality to manipulate package metadata and inflate developer reputation scores.

Vulnerability Detail

The vulnerability in teagood-lokina74 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 republishing of derivative packages, which pollutes the npm registry and can compromise the integrity of the ecosystem. The malicious scripts (auto.js, autopublish.js, etc.) are designed to execute these actions without user consent, posing significant risks to developers relying on the npm registry for trustworthy packages.

How To Fix

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

npm uninstall teagood-lokina74

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 removing it from your dependencies and replacing it with a trusted alternative. Additionally, monitor your package-lock.json file for any unauthorized changes.

Conclusion

The discovery of malicious code in the teagood-lokina74 package highlights the importance of vigilance in the npm ecosystem. Developers should take immediate action to remove affected packages and utilize tools like Vulert to monitor for vulnerabilities in their projects.

See every vulnerability recorded for teagood-lokina74 →

Share this vulnerability

FAQ

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

The malicious code modifies your package.json file, removes private flags, and generates random package names, which can lead to pollution of the npm registry and compromise your project's integrity.

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

Yes, you can use Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.

Regularly update your dependencies, monitor for vulnerabilities using tools like Vulert, and remove any packages that are flagged as malicious.

How To Fix

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

npm uninstall teagood-lokina74

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