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

teagood-sukuna11 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-167763: Malicious code in teagood-sukuna11 (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

teagood-sukuna11 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate the distribution of token rewards through various scripts. However, it has been identified as containing malicious code that modifies package metadata and repackages itself under different names, thereby compromising the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in teagood-sukuna11 originates from its malicious payload, which alters 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 to the npm registry. This behavior not only inflates developer reputation scores but also pollutes the npm registry with potentially harmful packages, posing a risk to developers who may unknowingly install these derivatives.

How To Fix

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

npm uninstall teagood-sukuna11

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-sukuna11 package altogether and look for alternative packages that provide similar functionality without the associated risks.

Conclusion

The teagood-sukuna11 package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial to uninstall this package and monitor your dependencies for vulnerabilities. Utilizing tools like Vulert can enhance your security posture by providing real-time alerts for open-source vulnerabilities.

See every vulnerability recorded for teagood-sukuna11 →

Share this vulnerability

FAQ

The primary risk is that it contains malicious code that modifies package metadata and floods the npm registry with harmful derivatives.

You can use Vulert, which monitors open-source vulnerabilities in your software. By uploading your package-lock.json file, you can receive real-time alerts about any vulnerabilities, including those related to teagood-sukuna11.

If you have installed teagood-sukuna11, you should uninstall it immediately using npm uninstall teagood-sukuna11 and check for any other affected packages.

Yes, consider using other npm packages that provide similar functionality without the malicious behavior. Always review package details and community feedback before installation.

Vulert uses your package-lock.json file to monitor and alert you in real-time for open-source vulnerabilities, helping you maintain the security of your application.

How To Fix

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

npm uninstall teagood-sukuna11

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