Malicious Code Injection in teagood-manaki31 Package - npm Vulnerability

teagood-manaki31 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-167096: Malicious code in teagood-manaki31 (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The teagood-manaki31 package is part of the tea.xyz token reward campaign, which has been known to flood the npm ecosystem with malicious packages. These packages are designed to manipulate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The primary functionality of this package is to participate in the token reward system, but its malicious nature poses significant risks to developers and the integrity of the npm registry.

Vulnerability Detail

The vulnerability in the teagood-manaki31 package originates from its design to include autopublish scripts that modify the package.json file. This modification removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants. The ramifications include pollution of the npm registry, potential security risks for developers using these packages, and a compromised reputation system within the npm ecosystem.

How To Fix

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

npm uninstall teagood-manaki31

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 workaround, you can manually remove the teagood-manaki31 package from your project by running the command: npm uninstall teagood-manaki31. Additionally, consider using tools like Vulert to monitor your project for any open-source vulnerabilities.

Conclusion

The teagood-manaki31 package poses a significant security risk due to its malicious code designed to manipulate npm's reputation system. It is essential for developers to take immediate action by removing this package and utilizing tools like Vulert to monitor for vulnerabilities in their projects.

See every vulnerability recorded for teagood-manaki31 →

Share this vulnerability

FAQ

teagood-manaki31 is an npm package associated with the tea.xyz token reward campaign, which has been identified as malicious.

The vulnerability can lead to the pollution of the npm registry and may compromise the security of your project by introducing malicious code.

You should immediately uninstall the teagood-manaki31 package and monitor your project for any further vulnerabilities.

Yes, Vulert allows you to monitor and alert for open-source vulnerabilities using just your package-lock.json file. You can check your application using the Vulert playground.

Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay updated on security advisories related to the packages you use.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall teagood-manaki31

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