Malicious Code Injection in teagood-yakuna75: A Threat to npm Packages

teagood-yakuna75 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-167937: Malicious code in teagood-yakuna75 (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

teagood-yakuna75 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate token rewards for developers by generating and publishing derivative packages. However, it has been identified as containing malicious code that compromises the integrity of the npm registry.

Vulnerability Detail

The vulnerability in teagood-yakuna75 stems from its malicious payload, which 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 to pollute the npm registry. This behavior not only affects the reputation of developers but also poses a risk of dependency confusion and potential exploitation of downstream projects.

How To Fix

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

npm uninstall teagood-yakuna75

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, you can avoid using the teagood-yakuna75 package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can use the following command to audit your npm packages for vulnerabilities: 'npm audit'.

Conclusion

The teagood-yakuna75 package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is essential for developers to take immediate action by removing the package and monitoring their applications for vulnerabilities. Utilizing tools like Vulert can help in maintaining the security of your software.

See every vulnerability recorded for teagood-yakuna75 →

Share this vulnerability

FAQ

The primary issue is that it contains malicious code that modifies package.json and floods the npm registry with derivative packages.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit the Vulert playground at Vulert Scanner to check if your application is affected without any signup.

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

Yes, consider looking for other npm packages that provide similar functionality without the associated risks. Always verify the package's reputation and security status.

Regularly audit your dependencies using 'npm audit', keep your packages updated, and monitor for security advisories related to the packages you use.

How To Fix

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

npm uninstall teagood-yakuna75

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