Malicious Code Injection in teagood-manaki56 Package: npm Vulnerability Overview

teagood-manaki56 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-167123: Malicious code in teagood-manaki56 (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-manaki56 package is part of the tea.xyz token reward campaign, which has been known to flood the npm registry with various packages. These packages are designed to automate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. The malicious behavior of this package poses significant risks to developers and the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in the teagood-manaki56 package originates from its inclusion in a campaign that employs autopublish scripts to manipulate package.json files. This manipulation removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants that pollute the npm registry. The ramifications include compromised developer reputations, potential security risks from unverified packages, and degradation of the npm ecosystem's reliability.

How To Fix

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

npm uninstall teagood-manaki56

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 temporarily avoid using the teagood-manaki56 package by removing it from your package.json file and running npm install to update your dependencies. Additionally, consider using alternative packages that do not exhibit malicious behavior.

Conclusion

The teagood-manaki56 package poses a significant risk due to its malicious code that manipulates package.json files and floods the npm registry. It is essential for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the integrity of their projects.

See every vulnerability recorded for teagood-manaki56 →

Share this vulnerability

FAQ

teagood-manaki56 is an npm package that is part of a campaign to generate and publish derivative packages for token rewards, which has been identified as malicious.

The vulnerability can lead to the pollution of the npm registry, compromising the integrity of your project's dependencies and potentially exposing it to security risks.

If you have installed the teagood-manaki56 package, it is crucial to remove it immediately and monitor your project for any related issues.

Yes, tools like Vulert can monitor your package-lock.json file for open-source vulnerabilities in real-time, alerting you to any issues without requiring code access.

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

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

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