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

teagood-nalikoli100 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-167508: Malicious code in teagood-nalikoli100 (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-nalikoli100 is an npm package that is part of the tea.xyz token reward campaign. It is designed to facilitate the distribution of token rewards through various packages. However, this package has been identified as containing malicious code that can compromise the integrity of the npm registry and the applications relying on it.

Vulnerability Detail

The vulnerability in teagood-nalikoli100 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 is intended to inflate developer reputation scores for token rewards, leading to pollution of the npm registry with derivative packages. The ramifications include potential security risks for applications that depend on these packages, as they may inadvertently use compromised versions.

How To Fix

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

npm uninstall teagood-nalikoli100

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 remove the teagood-nalikoli100 package from your project by executing: npm uninstall teagood-nalikoli100. This will prevent any malicious code from executing until a fix is applied.

Conclusion

The teagood-nalikoli100 package poses a significant risk due to its malicious code that alters package metadata and can lead to the creation of compromised packages. Users are advised to update or remove the package to safeguard their applications. Utilizing tools like Vulert can help in monitoring and identifying vulnerabilities in real-time.

See every vulnerability recorded for teagood-nalikoli100 →

Share this vulnerability

FAQ

The primary risk is the injection of malicious code that alters package metadata and can lead to the proliferation of compromised packages in the npm registry.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without requiring any signup.

If an immediate update is not possible, consider removing the package from your project as a temporary measure to mitigate risks.

While specific exploits have not been detailed, the nature of the vulnerability allows for the potential creation of numerous malicious packages that could affect users.

Regularly audit your dependencies, utilize tools like Vulert for monitoring vulnerabilities, and stay updated on 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-nalikoli100

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