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

teagood-sukuna69 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-167825: Malicious code in teagood-sukuna69 (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-sukuna69 is a package within the npm ecosystem, part of the tea.xyz token reward campaign. This campaign has been known to flood the npm registry with packages that contain malicious scripts. The primary function of these packages is to manipulate developer reputation scores through automated publishing of derivative packages, which can lead to significant pollution of the npm registry.

Vulnerability Detail

The vulnerability in teagood-sukuna69 stems from its inclusion in a malicious campaign that utilizes autopublish scripts to generate and publish numerous derivative packages with randomized names. This not only inflates developer reputation scores but also modifies the package.json file to remove private flags, alters version numbers, and continuously republishes variants. The ramifications of this vulnerability include potential security risks for developers who unknowingly integrate these malicious packages into their projects, leading to compromised applications and loss of trust in the npm ecosystem.

How To Fix

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

npm uninstall teagood-sukuna69

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, avoid using the teagood-sukuna69 package and consider using alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your npm packages using tools like npm audit to identify and mitigate vulnerabilities.

Conclusion

The teagood-sukuna69 package poses a significant risk due to its malicious nature, which can compromise the integrity of applications using it. Developers are urged to remove this package and monitor their projects for vulnerabilities to maintain security and trust in the npm ecosystem.

See every vulnerability recorded for teagood-sukuna69 →

Share this vulnerability

FAQ

teagood-sukuna69 is an npm package that is part of a malicious campaign aimed at manipulating developer reputation scores through automated publishing.

The vulnerability can lead to the inclusion of malicious code in your project, potentially compromising its security and integrity.

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

If you have used teagood-sukuna69, it is crucial to uninstall it immediately and audit your project for any dependencies that may have been affected.

Yes, tools like npm audit and Vulert can help you identify and manage vulnerabilities in your npm packages effectively.

How To Fix

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

npm uninstall teagood-sukuna69

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