Malicious Code Injection in teagood-manaki37 Package - npm Vulnerability

teagood-manaki37 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-167102: Malicious code in teagood-manaki37 (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 Penetration testing for web, API and mobile 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-manaki37 package is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The functionality of these packages is compromised due to the presence of malicious code that modifies essential package metadata.

Vulnerability Detail

The vulnerability originates from the malicious code embedded within the teagood-manaki37 package. This code is designed to alter the package.json file by removing private flags, changing version numbers, and generating random package names. The continuous republishing of these variants can lead to pollution of the npm registry, potentially affecting other developers and projects that rely on npm packages. The malicious payload poses a significant risk as it undermines the integrity of the npm ecosystem.

How To Fix

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

npm uninstall teagood-manaki37

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-manaki37 package and any other packages that are part of the tea.xyz token reward campaign. Monitor your package-lock.json file for any unauthorized changes and revert them if necessary.

Conclusion

The teagood-manaki37 package contains malicious code that compromises the integrity of the npm ecosystem. It is crucial for developers to uninstall this package and monitor their projects for any unauthorized changes. Utilizing tools like Vulert can help in identifying and managing vulnerabilities effectively.

See every vulnerability recorded for teagood-manaki37 →

Share this vulnerability

FAQ

teagood-manaki37 is an npm package associated with the tea.xyz token reward campaign, designed to inflate developer reputation scores.

The malicious code modifies your package.json file, potentially leading to unauthorized changes and pollution of the npm registry.

You should uninstall the teagood-manaki37 package immediately using 'npm uninstall teagood-manaki37' and check your project for any unauthorized changes.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. You can check your application for vulnerabilities without requiring access to the code or installation.

Yes, 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-manaki37

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