Malicious Code Injection in teagood-sukuna64 Package

teagood-sukuna64 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-167820: Malicious code in teagood-sukuna64 (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-sukuna64 package is part of the tea.xyz token reward campaign, which has been known to flood the npm ecosystem with various packages. These packages are designed to manipulate developer reputation scores through automated publishing scripts. The primary functionality of this package is to serve as a token reward mechanism, but its malicious nature compromises the integrity of the npm registry.

Vulnerability Detail

The vulnerability in the teagood-sukuna64 package stems from its inclusion in a series of malicious packages that contain scripts designed to automatically generate and publish derivative packages with randomized names. This behavior not only inflates developer reputation scores but also modifies the package.json file to remove private flags, alters version numbers, and continuously republishes variants, leading to pollution of the npm registry. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits npm's publishing mechanisms.

How To Fix

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

npm uninstall teagood-sukuna64

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-sukuna64 package and any other packages associated with the tea.xyz token reward campaign. Regularly audit your package dependencies using tools like npm audit to identify and mitigate potential vulnerabilities.

Conclusion

The teagood-sukuna64 package poses a significant risk due to its malicious code designed to manipulate npm's publishing system. It is crucial for developers to be vigilant about the packages they use and to regularly audit their dependencies to maintain the security of their projects.

See every vulnerability recorded for teagood-sukuna64 →

Share this vulnerability

FAQ

teagood-sukuna64 is an npm package associated with the tea.xyz token reward campaign, designed to manipulate developer reputation scores through automated publishing.

The vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of your project's dependencies and exposing it to further security risks.

If you have installed the teagood-sukuna64 package, you should uninstall it immediately using 'npm uninstall teagood-sukuna64' and audit your project for any other affected packages.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities. You can check your application against known vulnerabilities using the Vulert playground without any signup.

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

How To Fix

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

npm uninstall teagood-sukuna64

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