Malicious Code Injection in teagood-manaki7 Package: A Threat to npm Users

teagood-manaki7 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

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

The teagood-manaki7 package is part of the tea.xyz token reward campaign that has infiltrated the npm ecosystem. It is designed to facilitate the automatic generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. This package, like others in the campaign, is characterized by its use of autopublish scripts that can lead to significant pollution of the npm registry.

Vulnerability Detail

The vulnerability in teagood-manaki7 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 not only compromises the integrity of the npm registry but also poses a risk to developers who may unknowingly install these compromised packages. The continuous republishing of variants can lead to a cluttered ecosystem, making it difficult for developers to find legitimate packages.

How To Fix

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

npm uninstall teagood-manaki7

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 teagood-manaki7 package and monitor your dependencies for any unauthorized changes. Regularly audit your npm packages using npm audit to identify and address vulnerabilities.

Conclusion

The teagood-manaki7 package poses a significant risk due to its malicious code designed to manipulate the npm registry. It is crucial for developers to be aware of such vulnerabilities, take immediate action to remove affected packages, and utilize tools like Vulert for ongoing monitoring to safeguard their projects.

See every vulnerability recorded for teagood-manaki7 →

Share this vulnerability

FAQ

teagood-manaki7 is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages automatically.

The vulnerability can lead to the installation of malicious packages that may compromise your project's integrity and security.

You should uninstall the package immediately using the command npm uninstall teagood-manaki7 and check your project for any unauthorized changes.

Yes, tools like Vulert can help monitor and alert in real-time for open-source vulnerabilities in your software. You can check your application against known vulnerabilities using the Vulert playground.

Regularly audit your dependencies, keep your packages updated, and use tools like Vulert to monitor for vulnerabilities in real-time.

How To Fix

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

npm uninstall teagood-manaki7

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