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

teagood-sukuna35 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-167788: Malicious code in teagood-sukuna35 (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-sukuna35 is an npm package that is part of the tea.xyz token reward campaign, which has been known to flood the npm registry with various packages. This package is designed to interact with the tea protocol, offering token rewards to developers. However, it has been identified as containing malicious scripts that can compromise the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in teagood-sukuna35 stems from its inclusion of malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious payload can lead to the pollution of the npm registry, making it difficult for developers to find legitimate packages and potentially exposing their applications to further vulnerabilities.

How To Fix

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

npm uninstall teagood-sukuna35

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 workaround, you can avoid using the teagood-sukuna35 package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities.

Conclusion

The discovery of malicious code in the teagood-sukuna35 package highlights the importance of vigilance in the npm ecosystem. Developers are urged to remove this package and monitor their projects for vulnerabilities using tools like Vulert to ensure the security and integrity of their applications.

See every vulnerability recorded for teagood-sukuna35 →

Share this vulnerability

FAQ

teagood-sukuna35 is an npm package associated with the tea.xyz token reward campaign, which has been flagged for containing malicious code.

The malicious code can modify your package.json file, remove private flags, and publish derivative packages, leading to potential security risks and pollution of the npm registry.

You should uninstall the package immediately using 'npm uninstall teagood-sukuna35' and check for any alternative packages.

Yes, you can use Vulert, which monitors your package-lock.json file for vulnerabilities in real-time without requiring code access or installation.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without signing up.

How To Fix

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

npm uninstall teagood-sukuna35

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