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

teagood-lokina61 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-167028: Malicious code in teagood-lokina61 (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-lokina61 is an npm package that appears to be part of a broader campaign aimed at exploiting the npm registry for token rewards associated with the tea.xyz protocol. This package is designed to automate the creation and publishing of derivative packages, which can lead to reputation inflation for developers involved in the campaign. The malicious nature of this package poses a significant risk to the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in teagood-lokina61 originates from its design to include autopublish scripts that modify the package.json file. These scripts remove private flags, alter version numbers, and generate random package names, ultimately leading to the continuous republishing of variants. This behavior not only pollutes the npm registry but also compromises the security and reliability of the packages available to developers. The malicious payload can potentially affect any project that inadvertently includes this package, leading to further exploitation.

How To Fix

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

npm uninstall teagood-lokina61

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 measure, you can avoid using the teagood-lokina61 package and any other packages that may have been derived from it. Monitor your package-lock.json file for any unexpected changes or additions that may indicate the presence of malicious packages.

Conclusion

The teagood-lokina61 package poses a significant risk due to its malicious code designed to exploit the npm registry. It is crucial for developers to be vigilant about the packages they include in their projects and to take immediate action to remove any affected packages. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.

See every vulnerability recorded for teagood-lokina61 →

Share this vulnerability

FAQ

teagood-lokina61 is an npm package associated with a malicious campaign that aims to exploit the npm registry for token rewards.

The vulnerability can lead to the inclusion of malicious code in your project, potentially compromising its security and integrity.

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

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

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-lokina61

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