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

teagood-manaki8 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-167148: Malicious code in teagood-manaki8 (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-manaki8 is an npm package that is part of a broader campaign associated with the tea.xyz token reward system. This package is designed to facilitate the automatic generation and publication of derivative packages, often with randomized names, to manipulate developer reputation scores for token rewards. The malicious nature of this package poses significant risks to the integrity of the npm registry and the security of applications relying on it.

Vulnerability Detail

The vulnerability in teagood-manaki8 stems from its malicious code that modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the continuous republishing of variants, effectively polluting the npm registry. The origin of this vulnerability is linked to a campaign aimed at exploiting npm's package management system for fraudulent token rewards, which can result in compromised applications and degraded trust in the npm ecosystem.

How To Fix

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

npm uninstall teagood-manaki8

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-manaki8 package and any other packages associated with the tea.xyz token reward campaign. Regularly audit your dependencies to ensure that no malicious packages are included in your project.

Conclusion

The teagood-manaki8 package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remove this package and monitor their dependencies for similar threats to maintain the security and integrity of their applications.

See every vulnerability recorded for teagood-manaki8 →

Share this vulnerability

FAQ

teagood-manaki8 is an npm package involved in a malicious campaign that aims to manipulate developer reputation scores for token rewards.

The vulnerability can lead to the modification of your package.json file, potentially compromising your application's integrity and security.

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

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

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

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