Malicious Code Injection in teagood-sukuna42 Package

teagood-sukuna42 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-167796: Malicious code in teagood-sukuna42 (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

The teagood-sukuna42 package is part of a broader campaign associated with the tea.xyz token reward system, which has been known to flood the npm registry with various packages. This package, like others in the campaign, is designed to manipulate npm's publishing system, potentially affecting developers' reputations and the integrity of the npm ecosystem. Its functionality revolves around generating and publishing derivative packages, which can lead to significant pollution of the npm registry.

Vulnerability Detail

The vulnerability in the teagood-sukuna42 package stems from its malicious code that modifies the package.json file to remove private flags and alters version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants. This behavior not only inflates developer reputation scores for the tea protocol but also poses a risk of flooding the npm registry with potentially harmful packages, making it difficult for developers to find legitimate packages.

How To Fix

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

npm uninstall teagood-sukuna42

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, consider using a package-lock.json file to monitor and control the versions of packages used in your project. This can help prevent the installation of malicious packages. Additionally, you can use tools like Vulert to monitor your dependencies for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without needing to sign up.

Conclusion

The teagood-sukuna42 package presents a significant risk due to its malicious code that alters package metadata and floods the npm registry with harmful variants. It is crucial for developers to be aware of this vulnerability, take immediate action to remove the package, and utilize monitoring tools like Vulert to safeguard their projects against future threats.

See every vulnerability recorded for teagood-sukuna42 →

Share this vulnerability

FAQ

teagood-sukuna42 is an npm package associated with the tea.xyz token reward campaign, designed to manipulate the npm registry.

The vulnerability can lead to the pollution of the npm registry with malicious packages, making it harder to find legitimate packages and potentially compromising your project's security.

You should uninstall the teagood-sukuna42 package immediately and monitor your project for any other potentially malicious dependencies.

Using tools like Vulert can help monitor your dependencies for vulnerabilities in real-time, allowing you to take action before they affect your project.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by vulnerabilities without requiring any signup.

How To Fix

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

npm uninstall teagood-sukuna42

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