Malicious Code Injection in teagood-nalikami5 Package - npm Vulnerability

teagood-nalikami5 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-167450: Malicious code in teagood-nalikami5 (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 Your last release was probably never penetration tested 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-nalikami5 package is part of the tea.xyz token reward campaign that has infiltrated the npm ecosystem. This package, like others in the campaign, is designed to manipulate npm's publishing system by generating and publishing derivative packages with randomized names. Its primary function is to inflate developer reputation scores for token rewards, but it poses significant risks due to its malicious behavior.

Vulnerability Detail

The vulnerability in the teagood-nalikami5 package stems from its inclusion in a campaign that uses autopublish scripts to create and publish numerous derivative packages. These scripts modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior can lead to pollution of the npm registry, making it difficult for developers to find legitimate packages and potentially exposing them to malicious code.

How To Fix

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

npm uninstall teagood-nalikami5

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 avoid using the teagood-nalikami5 package altogether. If it is already in your project, consider removing it and replacing it with a trusted alternative. You can also use tools like Vulert to monitor your package-lock.json for vulnerabilities in real-time.

Conclusion

The teagood-nalikami5 package poses a significant risk due to its malicious code designed to manipulate npm's publishing system. It is crucial for developers to remove this package and monitor their projects for vulnerabilities using tools like Vulert to ensure the security of their applications.

See every vulnerability recorded for teagood-nalikami5 →

Share this vulnerability

FAQ

teagood-nalikami5 is an npm package that is part of a token reward campaign, which has been identified to contain malicious code.

The malicious code modifies your package.json file and can lead to the publication of numerous derivative packages, polluting the npm registry and potentially introducing security risks.

You should remove the teagood-nalikami5 package from your project and monitor for any updates or patches that may be released.

You can use Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access or installation.

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-nalikami5

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