Malicious Code Injection in teagood-sukuna60 Package

teagood-sukuna60 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-167816: Malicious code in teagood-sukuna60 (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-sukuna60 package is part of the tea.xyz token reward campaign, which has been known to flood the npm ecosystem with packages designed to inflate developer reputation scores. These packages often contain scripts that automatically generate and publish derivative packages with randomized names, which can lead to pollution of the npm registry and potential security risks for developers using these packages.

Vulnerability Detail

The vulnerability in the teagood-sukuna60 package originates from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to continuously republish variants, thereby polluting the npm registry and potentially compromising the integrity of applications that depend on these packages. The malicious code can lead to unauthorized access, data breaches, and a compromised development environment.

How To Fix

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

npm uninstall teagood-sukuna60

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

There are no specific workarounds for this vulnerability other than uninstalling the affected package. If you need similar functionality, consider looking for alternative packages that are well-maintained and have a good reputation in the community.

Conclusion

The teagood-sukuna60 package poses a significant security risk due to its malicious code that modifies package metadata and repopulates the npm registry with potentially harmful variants. It is crucial for developers to uninstall this package and monitor their projects for vulnerabilities to maintain a secure development environment.

See every vulnerability recorded for teagood-sukuna60 →

Share this vulnerability

FAQ

teagood-sukuna60 is a package associated with the tea.xyz token reward campaign, which aims to inflate developer reputation scores through the creation of numerous derivative packages.

The vulnerability can lead to the pollution of the npm registry, potentially introducing malicious code into your application and compromising its security.

You should uninstall the teagood-sukuna60 package immediately using the command: npm uninstall teagood-sukuna60.

No patches are available for this specific package, and it is recommended to avoid using it altogether.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file. You can check if your application is affected by this vulnerability using the Vulert playground at Vulert Scanner without any signup.

How To Fix

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

npm uninstall teagood-sukuna60

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