Malicious Code Injection in teagood-manaki42 Package

teagood-manaki42 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-167108: Malicious code in teagood-manaki42 (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-manaki42 package is part of the tea.xyz token reward campaign, which has been associated with a series of malicious npm packages. These packages are designed to inflate developer reputation scores through the automatic generation and publication of derivative packages with randomized names. The primary functionality of these packages is to manipulate the npm registry by continuously republishing variants, thereby polluting the ecosystem.

Vulnerability Detail

The vulnerability in the teagood-manaki42 package stems from its malicious payload that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, primarily themed around Indonesian culture. This behavior is indicative of a broader trend where such packages are used to exploit the npm registry, leading to potential security risks for developers who inadvertently install these compromised packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which has flooded the npm ecosystem with similar malicious packages.

How To Fix

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

npm uninstall teagood-manaki42

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 avoid using the teagood-manaki42 package and any other packages associated with the tea.xyz campaign. Consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The teagood-manaki42 package poses a significant security risk due to its malicious code that alters package metadata and floods the npm registry with compromised packages. It is essential to remove this package from your project and monitor your dependencies for similar vulnerabilities. Utilizing tools like Vulert can help you stay informed about potential threats in your software.

See every vulnerability recorded for teagood-manaki42 →

Share this vulnerability

FAQ

teagood-manaki42 is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the automatic publication of derivative packages.

The vulnerability can lead to the modification of your package.json file, removal of private flags, and the introduction of potentially harmful packages into your project.

You should uninstall the teagood-manaki42 package immediately and check your project for any other potentially compromised packages.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities. You can check your application for vulnerabilities using the Vulert playground without any signup.

Yes, consider using other reputable npm packages that provide similar functionality without the associated risks of malicious behavior.

How To Fix

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

npm uninstall teagood-manaki42

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