Malicious Code Injection in teagood-manaki19 Package

teagood-manaki19 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-167082: Malicious code in teagood-manaki19 (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The teagood-manaki19 package is part of the tea.xyz token reward campaign, which has been known to flood the npm registry with packages. These packages are designed to inflate developer reputation scores through automated scripts that publish derivative packages with randomized names. The malicious nature of this package lies in its ability to modify critical files and republish variants, thereby polluting the npm registry.

Vulnerability Detail

The vulnerability in the teagood-manaki19 package originates from its inclusion in a campaign that utilizes autopublish scripts to generate and publish numerous derivative packages. The malicious payload modifies the package.json file by removing private flags, altering version numbers, and creating random package names. This behavior can lead to significant pollution of the npm registry, making it difficult for developers to find legitimate packages and potentially exposing them to security risks.

How To Fix

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

npm uninstall teagood-manaki19

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 remove the teagood-manaki19 package from your project by executing the following command: npm uninstall teagood-manaki19. This will prevent any malicious code from executing while you seek a permanent fix.

Conclusion

The teagood-manaki19 package poses a significant risk due to its malicious code that modifies package files and repopulates the npm registry with derivative packages. It is crucial to take immediate action by uninstalling the package and monitoring your project for vulnerabilities using tools like Vulert.

See every vulnerability recorded for teagood-manaki19 →

Share this vulnerability

FAQ

teagood-manaki19 is an npm package that is part of a token reward campaign, which has been identified as malicious due to its behavior of publishing derivative packages.

The vulnerability can lead to pollution of the npm registry, making it harder to find legitimate packages and potentially exposing your project to security risks.

You should uninstall the package immediately and check for any updates or patches from the package maintainers.

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

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

How To Fix

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

npm uninstall teagood-manaki19

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