Malicious Code Injection in teagood-manaki14: A Threat to npm Ecosystem

teagood-manaki14 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-167077: Malicious code in teagood-manaki14 (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

teagood-manaki14 is an npm package that is part of the tea.xyz token reward campaign. This package, like many others in the campaign, is designed to manipulate the npm registry by generating and publishing derivative packages with randomized names. The primary functionality of this package is to inflate developer reputation scores for rewards associated with the tea protocol, but it has been compromised to include malicious scripts.

Vulnerability Detail

The vulnerability in teagood-manaki14 originates from its inclusion in a malicious campaign that floods the npm registry with derivative packages. The malicious payload modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly install these compromised packages, potentially leading to further exploitation.

How To Fix

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

npm uninstall teagood-manaki14

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-manaki14 package and any other packages associated with the tea.xyz token reward campaign. Additionally, consider using package-lock.json to monitor dependencies and ensure that no malicious packages are included in your project.

Conclusion

The vulnerability in teagood-manaki14 poses a significant risk to the npm ecosystem by enabling malicious code to manipulate package metadata and pollute the registry. It is crucial for developers to be vigilant and remove any affected packages while utilizing tools like Vulert to monitor for vulnerabilities in their projects.

See every vulnerability recorded for teagood-manaki14 →

Share this vulnerability

FAQ

teagood-manaki14 is an npm package that is part of a campaign designed to inflate developer reputation scores for token rewards, but it has been compromised to include malicious code.

The malicious code modifies your package.json file, removes private flags, and continuously republishes variants, which can lead to pollution of the npm registry and potential exploitation.

You should uninstall the package immediately using 'npm uninstall teagood-manaki14' and check for any other affected packages in your project.

Yes, you can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access or installation.

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

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