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

teagood-yakuna49 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-167908: Malicious code in teagood-yakuna49 (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-yakuna49 is an npm package that appears to be part of a token reward campaign associated with the tea.xyz protocol. This package is designed to generate and publish derivative packages with randomized names, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises the integrity of the npm registry.

Vulnerability Detail

The vulnerability in teagood-yakuna49 originates 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 can lead to a compromised development environment, where developers may unknowingly install malicious packages, jeopardizing their applications and systems.

How To Fix

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

npm uninstall teagood-yakuna49

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, avoid using the teagood-yakuna49 package and any derivatives that may have been published. Regularly audit your package dependencies using tools like npm audit to identify and mitigate vulnerabilities.

Conclusion

The discovery of malicious code in the teagood-yakuna49 package highlights the importance of vigilance when using open-source packages. Developers should take immediate action to remove the affected package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can enhance security by providing real-time alerts for open-source vulnerabilities.

See every vulnerability recorded for teagood-yakuna49 →

Share this vulnerability

FAQ

teagood-yakuna49 is an npm package associated with a token reward campaign that has been found to contain malicious code.

The malicious code modifies your package.json file, removes private flags, and can lead to the installation of compromised packages, affecting the security of your project.

You should uninstall the package immediately using 'npm uninstall teagood-yakuna49' and check for any dependencies that may be affected.

You can use tools like npm audit to check for vulnerabilities in your packages. Additionally, Vulert can monitor your package-lock.json for real-time alerts on open-source vulnerabilities.

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

How To Fix

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

npm uninstall teagood-yakuna49

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