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

teagood-nalikoli79 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-167637: Malicious code in teagood-nalikoli79 (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-nalikoli79 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 inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. Its functionality is compromised due to the presence of malicious code that alters package metadata and floods the npm registry with unwanted variants.

Vulnerability Detail

The vulnerability in teagood-nalikoli79 originates from its malicious payload, which modifies the package.json file to remove private flags and changes version numbers. It generates random Indonesian-themed package names and continuously republishes these variants, polluting the npm registry. This can lead to significant issues for developers, including the potential for reputation damage and the risk of inadvertently using compromised packages in their projects.

How To Fix

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

npm uninstall teagood-nalikoli79

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 measure, you can avoid using the teagood-nalikoli79 package and monitor your project dependencies for any instances of this package. You can also utilize tools like Vulert to monitor your package-lock.json for vulnerabilities. Here’s how to check your application:

  1. Visit the Vulert playground at https://vulert.com/scanner.
  2. Upload your package-lock.json file.
  3. Review the results for any vulnerabilities, including the one associated with teagood-nalikoli79.

Conclusion

The teagood-nalikoli79 package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the security of their projects.

See every vulnerability recorded for teagood-nalikoli79 →

Share this vulnerability

FAQ

teagood-nalikoli79 is an npm package involved in a token reward campaign that generates and publishes derivative packages to inflate developer reputation scores.

The vulnerability can lead to the introduction of malicious code into your project, potentially compromising its security and integrity.

You should remove the teagood-nalikoli79 package from your project immediately and check for any other affected packages.

Yes, you can use Vulert to monitor your package-lock.json file for vulnerabilities in real-time without needing to install any software.

Regularly update your packages, review their integrity, and utilize tools like Vulert to keep track of vulnerabilities in your dependencies.

How To Fix

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

npm uninstall teagood-nalikoli79

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