Malicious Code Injection in teagood-manaki28 Package - npm Vulnerability

teagood-manaki28 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

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

The teagood-manaki28 package is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to manipulate npm's registry by generating and publishing derivative packages with randomized names. The primary function of these packages is to inflate developer reputation scores for token rewards, which poses significant risks to the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in the teagood-manaki28 package stems from its malicious payload that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants. This behavior not only pollutes the npm registry but also compromises the security of projects that depend on these packages, potentially introducing further vulnerabilities and instability.

How To Fix

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

npm uninstall teagood-manaki28

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-manaki28 package and any other related packages from the tea.xyz campaign. Regularly audit your dependencies to ensure that no malicious packages are included in your project.

Conclusion

The teagood-manaki28 package poses a significant threat due to its malicious code designed to manipulate npm's registry. It is crucial for developers to remove this package and monitor their dependencies to maintain the integrity and security of their projects.

See every vulnerability recorded for teagood-manaki28 →

Share this vulnerability

FAQ

teagood-manaki28 is an npm package that is part of a campaign to manipulate npm's registry for token rewards, often containing malicious code.

The vulnerability can lead to the introduction of malicious code, which may compromise your project's security and stability.

You should uninstall the package immediately using 'npm uninstall teagood-manaki28' and audit your dependencies for any other malicious packages.

Yes, you can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.

How To Fix

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

npm uninstall teagood-manaki28

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