Malicious Code Vulnerability in teagood-manaki38 Package

teagood-manaki38 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-167103: Malicious code in teagood-manaki38 (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-manaki38 package is part of a larger ecosystem associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with various packages. This package, like others in its category, is designed to manipulate developer reputation scores through the automatic generation and publication of derivative packages. Its functionality is compromised due to the presence of malicious scripts that alter package metadata and republish variants, leading to potential security risks for developers and users alike.

Vulnerability Detail

The vulnerability in the teagood-manaki38 package originates from its inclusion in a malicious campaign that utilizes autopublish scripts to create and disseminate numerous derivative packages with randomized names. This behavior not only pollutes the npm registry but also modifies critical files like package.json by removing private flags and changing version numbers. The ramifications include the risk of developers unknowingly using compromised packages, which can lead to security breaches and loss of trust in the npm ecosystem.

How To Fix

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

npm uninstall teagood-manaki38

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 avoid using the teagood-manaki38 package altogether. If it is already included in your project, consider removing it and replacing it with a trusted alternative. Additionally, you can monitor your package dependencies using tools like Vulert, which can alert you to vulnerabilities in real-time without requiring code access or installation.

Conclusion

The teagood-manaki38 package poses a significant security risk due to its malicious code that alters package metadata and repopulates the npm registry with compromised variants. It is crucial 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-manaki38 →

Share this vulnerability

FAQ

teagood-manaki38 is an npm package associated with the tea.xyz token reward campaign, which is known for flooding the npm registry with malicious packages.

The vulnerability can lead to the inclusion of compromised packages in your project, which may result in security breaches and loss of trust in your software.

You should remove the teagood-manaki38 package from your project and monitor for any updates or patches that may address the vulnerability.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

Vulert is a tool that monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file, providing real-time insights into potential risks.

How To Fix

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

npm uninstall teagood-manaki38

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