Malicious Code Injection in teagood-manaki54 Package

teagood-manaki54 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-167121: Malicious code in teagood-manaki54 (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-manaki54 package is part of the tea.xyz token reward campaign, which has been known to flood the npm ecosystem with various packages. These packages are designed to manipulate developer reputation scores through automated publishing scripts. The package's functionality revolves around generating and publishing derivative packages with randomized names, which can lead to significant pollution of the npm registry.

Vulnerability Detail

The vulnerability in the teagood-manaki54 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, leading to potential security breaches and loss of trust in the ecosystem.

How To Fix

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

npm uninstall teagood-manaki54

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 remove the package from your project by executing the following command in your terminal: npm uninstall teagood-manaki54. This will help mitigate the risk associated with the malicious code present in the package.

Conclusion

The teagood-manaki54 package poses a significant risk due to its malicious code that alters package metadata and publishes compromised versions. It is crucial for developers to remove this package from their projects and stay vigilant by utilizing tools like Vulert to monitor for vulnerabilities in their dependencies.

See every vulnerability recorded for teagood-manaki54 →

Share this vulnerability

FAQ

teagood-manaki54 is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through automated publishing.

The vulnerability can lead to the injection of malicious code into your project, potentially compromising its security and integrity.

You should uninstall the teagood-manaki54 package immediately and monitor your project for any unusual behavior.

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

Absolutely! 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-manaki54

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