Malicious Code Injection in teagood-namakai35: A Threat to npm Packages

teagood-namakai35 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-167689: Malicious code in teagood-namakai35 (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-namakai35 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to interact with the npm ecosystem, primarily for the purpose of generating and publishing derivative packages. It is characterized by its use of autopublish scripts that create numerous variants of itself, often with randomized names, to inflate developer reputation scores for token rewards. The package has been identified as malicious due to its ability to modify critical files and republish itself, leading to potential pollution of the npm registry.

Vulnerability Detail

The vulnerability in teagood-namakai35 originates from its malicious payload, which modifies the package.json file by removing private flags and changing version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants. This behavior not only compromises the integrity of the npm registry but also poses a risk to developers who may unknowingly install these malicious packages, leading to potential security breaches in their applications.

How To Fix

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

npm uninstall teagood-namakai35

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-namakai35 package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for any unauthorized changes in the package.json and package-lock.json files.

Conclusion

The discovery of malicious code in the teagood-namakai35 package highlights the importance of vigilance in managing npm packages. By understanding the nature of this vulnerability and taking appropriate action, developers can protect their projects from potential threats. Regular monitoring and using tools like Vulert can further enhance security measures.

See every vulnerability recorded for teagood-namakai35 →

Share this vulnerability

FAQ

teagood-namakai35 is an npm package involved in the tea.xyz token reward campaign, designed to generate and publish derivative packages.

The vulnerability can lead to unauthorized modifications in your package.json file and the potential installation of malicious variants, compromising your project's security.

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

Yes, tools like Vulert can monitor your package-lock.json file for open-source vulnerabilities in real-time, alerting you to any issues.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

How To Fix

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

npm uninstall teagood-namakai35

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