Malicious Code Injection in teagood-manaki96 Package

teagood-manaki96 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-167166: Malicious code in teagood-manaki96 (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-manaki96 package is part of the tea.xyz token reward campaign that has infiltrated the npm ecosystem. This package is designed to facilitate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. Its functionality is primarily centered around automating the publishing process, which unfortunately makes it susceptible to exploitation.

Vulnerability Detail

The vulnerability in the teagood-manaki96 package stems from its inclusion in a malicious campaign that 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 use these compromised packages. The malicious payload continuously republishes variants, leading to pollution of the npm ecosystem and potential security risks for users.

How To Fix

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

npm uninstall teagood-manaki96

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, consider using a package-lock.json file to lock your dependencies to specific versions. This can help prevent the installation of compromised packages. You can also monitor your dependencies using tools like Vulert, which alerts you to open-source vulnerabilities in real-time without requiring code access or installation.

Conclusion

The teagood-manaki96 package poses a significant risk due to its malicious code that alters package metadata and repopulates the npm registry with compromised packages. It is essential to take immediate action to remove this package and monitor your dependencies for vulnerabilities. Utilizing tools like Vulert can enhance your security posture by providing real-time alerts for open-source vulnerabilities.

See every vulnerability recorded for teagood-manaki96 →

Share this vulnerability

FAQ

teagood-manaki96 is a package associated with the tea.xyz token reward campaign, designed to automate the generation and publication of npm packages.

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

You should uninstall the package immediately using 'npm uninstall teagood-manaki96' and monitor your project for any other vulnerable dependencies.

Using tools like Vulert can help monitor your dependencies for vulnerabilities in real-time, allowing you to take action before issues arise.

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

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