Malicious Code Vulnerability in teagood-manaki77 Package

teagood-manaki77 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-167145: Malicious code in teagood-manaki77 (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-manaki77 package is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to automate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. The package's functionality is compromised due to the presence of malicious code that alters its metadata and behavior.

Vulnerability Detail

The vulnerability originates from a malicious payload embedded within the teagood-manaki77 package. This payload modifies the package.json file by removing private flags, changing version numbers, and generating random package names, which leads to the continuous republishing of these variants. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, potentially leading to further exploitation.

How To Fix

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

npm uninstall teagood-manaki77

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 remove the teagood-manaki77 package from your project by executing the following command: npm uninstall teagood-manaki77. Additionally, ensure that your package-lock.json file is monitored for any unauthorized changes.

Conclusion

The teagood-manaki77 package contains a serious vulnerability due to malicious code that alters its functionality and metadata. It is crucial for developers to take immediate action by uninstalling the package and monitoring their projects for any unauthorized changes. Utilizing tools like Vulert can help in identifying and mitigating such vulnerabilities in the future.

See every vulnerability recorded for teagood-manaki77 →

Share this vulnerability

FAQ

teagood-manaki77 is an npm package that is part of a campaign to generate and publish derivative packages for token rewards, but it contains malicious code.

The malicious code modifies your package.json file, removes private flags, and generates random package names, which can lead to further exploitation and pollution of the npm registry.

You should uninstall the teagood-manaki77 package immediately and monitor your project for any unauthorized changes.

Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software using just package-lock.json. You can check if your application is affected by visiting the Vulert playground.

Regularly update your dependencies, monitor your package-lock.json for changes, and utilize tools like Vulert to stay informed about vulnerabilities.

How To Fix

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

npm uninstall teagood-manaki77

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