Malicious Code Injection in teagood-nalikoli44: A Threat to npm Users

teagood-nalikoli44 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-167599: Malicious code in teagood-nalikoli44 (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

teagood-nalikoli44 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to interact with the npm registry, allowing developers to publish and manage their 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 harmful scripts.

Vulnerability Detail

The vulnerability in teagood-nalikoli44 originates from its malicious payload, which modifies the package.json file to remove private flags and changes version numbers. This allows the package to generate random names for derivative packages, which are then continuously republished to pollute the npm registry. The malicious scripts (auto.js, autopublish.js, etc.) are designed to inflate developer reputation scores for token rewards, posing a significant risk to developers and users relying on the integrity of the npm ecosystem.

How To Fix

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

npm uninstall teagood-nalikoli44

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, you can avoid using the teagood-nalikoli44 package and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly monitor your dependencies for vulnerabilities using tools like Vulert, which can alert you to open-source vulnerabilities in real-time.

Conclusion

The discovery of malicious code in the teagood-nalikoli44 npm package highlights the importance of vigilance in managing dependencies. Developers should take immediate action to remove this package and utilize tools like Vulert to monitor their projects for vulnerabilities. Staying informed and proactive can help maintain the integrity of the software ecosystem.

See every vulnerability recorded for teagood-nalikoli44 →

Share this vulnerability

FAQ

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

The malicious code modifies package.json files, removes private flags, and generates random package names, leading to potential pollution of the npm registry and compromising your project's integrity.

You should uninstall the package immediately using npm uninstall teagood-nalikoli44 and monitor your project for any unusual behavior.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for 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-nalikoli44

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