Malicious Code Injection in teagood-nakama82: A Threat to npm Users

teagood-nakama82 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

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

teagood-nakama82 is a package that was part of the tea.xyz token reward campaign, which aimed to incentivize developers through token rewards. This package, like others in the campaign, is designed to manipulate the npm registry by generating and publishing derivative packages with randomized names. The malicious nature of this package lies in its ability to alter package metadata and republish variants, potentially harming the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in teagood-nakama82 originates from its malicious code that modifies the package.json file to remove private flags, changes version numbers, and generates random package names. This behavior is intended to inflate developer reputation scores for token rewards, leading to pollution of the npm registry with numerous derivative packages. The ramifications include compromised package integrity, potential security risks for applications relying on these packages, and degradation of the npm ecosystem's trustworthiness.

How To Fix

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

npm uninstall teagood-nakama82

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

Conclusion

The discovery of malicious code in teagood-nakama82 highlights the importance of vigilance when using open-source packages. By understanding the risks and taking proactive measures, developers can protect their applications and maintain the integrity of the npm ecosystem.

See every vulnerability recorded for teagood-nakama82 →

Share this vulnerability

FAQ

teagood-nakama82 is an npm package that was part of a token reward campaign, which has been identified as containing malicious code.

The malicious code modifies package metadata and can lead to the publication of numerous derivative packages, potentially compromising the integrity of your application.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without needing to sign up.

If you have installed teagood-nakama82, it is crucial to uninstall it immediately using npm uninstall teagood-nakama82.

Yes, consider looking for other npm packages that provide similar functionality without the associated risks of malicious code.

How To Fix

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

npm uninstall teagood-nakama82

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