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

teagood-sukuna18 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-167770: Malicious code in teagood-sukuna18 (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-sukuna18 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to interact with the npm registry and is typically used for publishing JavaScript packages. However, it has been identified as containing malicious code that can compromise the integrity of the npm ecosystem by generating and publishing derivative packages with random names.

Vulnerability Detail

The vulnerability in teagood-sukuna18 originates from its design to include autopublish scripts that modify the package.json file. These scripts remove private flags, alter version numbers, and generate random package names, which leads to the pollution of the npm registry. This can inflate developer reputation scores fraudulently and potentially introduce harmful packages to users. The malicious behavior can affect developers relying on the integrity of the npm ecosystem, leading to security risks and loss of trust.

How To Fix

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

npm uninstall teagood-sukuna18

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 measure, avoid using the teagood-sukuna18 package and monitor your project for any unintended dependencies that may have been introduced. You can also use tools like Vulert to monitor your package-lock.json for vulnerabilities.

Conclusion

The discovery of malicious code in the teagood-sukuna18 package highlights the importance of vigilance in the npm ecosystem. Developers should take immediate action to remove this package and monitor their projects for vulnerabilities. Utilizing tools like Vulert can aid in maintaining the security of your applications.

See every vulnerability recorded for teagood-sukuna18 →

Share this vulnerability

FAQ

teagood-sukuna18 is an npm package associated with the tea.xyz token reward campaign, which has been identified to contain malicious code.

The malicious code can modify your package.json, remove private flags, and publish harmful packages, potentially compromising your project's integrity.

You should uninstall the package immediately using 'npm uninstall teagood-sukuna18' and check for any other affected packages.

You can use Vulert to monitor your package-lock.json for vulnerabilities in real-time without needing to access the code or install additional software.

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

How To Fix

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

npm uninstall teagood-sukuna18

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