Malicious Code Injection in teagood-manaki72 Package - npm Vulnerability

teagood-manaki72 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-167140: Malicious code in teagood-manaki72 (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 Your last release was probably never penetration tested 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-manaki72 package is part of a series of packages associated with the tea.xyz token reward campaign, which has been known to flood the npm registry. 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 malicious nature of this package lies in its ability to modify critical files and republish variants, thereby polluting the npm ecosystem.

Vulnerability Detail

The vulnerability in the teagood-manaki72 package 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 can lead to the proliferation of unwanted packages in the npm registry, potentially compromising the integrity of applications that depend on legitimate packages. The continuous republishing of these variants can also lead to confusion and difficulty in managing dependencies for developers.

How To Fix

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

npm uninstall teagood-manaki72

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 prevent the installation of this malicious package by using npm's package-lock.json file to lock your dependencies. Ensure that your project does not include the teagood-manaki72 package or any of its derivatives.

Conclusion

The teagood-manaki72 package presents a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is essential for developers to remove this package and monitor their dependencies for similar vulnerabilities to maintain the integrity of their applications.

See every vulnerability recorded for teagood-manaki72 →

Share this vulnerability

FAQ

teagood-manaki72 is an npm package associated with the tea.xyz token reward campaign, known for flooding the npm registry with malicious packages.

This vulnerability can lead to the proliferation of malicious packages in your project, potentially compromising its integrity and security.

You should uninstall the teagood-manaki72 package immediately and ensure your project dependencies are secure.

Yes, you can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

How To Fix

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

npm uninstall teagood-manaki72

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