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

teagood-nalikami134 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-167409: Malicious code in teagood-nalikami134 (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-nalikami134 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 malicious, containing scripts that manipulate package metadata and flood the npm registry with unwanted variants.

Vulnerability Detail

The vulnerability in teagood-nalikami134 originates from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior not only inflates developer reputation scores fraudulently but also pollutes the npm registry, making it difficult for legitimate packages to be discovered. The scripts involved are typically named auto.js, autopublish.js, autopublish2.js, and autopublish3.js, and they continuously republish variants, exacerbating the issue.

How To Fix

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

npm uninstall teagood-nalikami134

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 monitor your project for vulnerabilities using tools like Vulert. By analyzing your package-lock.json file, Vulert can alert you in real-time about any open-source vulnerabilities. You can also 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 discovery of malicious code in the teagood-nalikami134 package highlights the importance of vigilance in managing npm packages. By understanding the nature of this vulnerability and taking proactive steps to mitigate risks, developers can protect their projects from potential threats.

See every vulnerability recorded for teagood-nalikami134 →

Share this vulnerability

FAQ

teagood-nalikami134 is an npm package associated with the tea.xyz token reward campaign, which aims to incentivize developers through token rewards.

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 integrity.

You should immediately uninstall the package using npm uninstall teagood-nalikami134 and check for any other affected packages in your project.

You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities and alerts you in real-time.

Regularly update your dependencies, use trusted packages, and employ vulnerability scanning tools to help identify and mitigate risks.

How To Fix

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

npm uninstall teagood-nalikami134

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