Malicious Code Injection in teagood-nalikoli60: A Threat to npm Ecosystem

teagood-nalikoli60 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-167617: Malicious code in teagood-nalikoli60 (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

teagood-nalikoli60 is an npm package that is part of a larger campaign aimed at exploiting the npm registry for token rewards associated with the tea.xyz protocol. This package, like others in the campaign, is designed to manipulate the npm ecosystem by generating and publishing numerous derivative packages with the intent of inflating developer reputation scores. The malicious nature of this package poses significant risks to developers and users relying on npm for package management.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the teagood-nalikoli60 package. This code modifies the package.json file to remove private flags, alters version numbers, and creates random package names, which leads to the continuous republishing of these variants. The primary risk is that it pollutes the npm registry, making it difficult for developers to find legitimate packages and potentially compromising the integrity of their applications.

How To Fix

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

npm uninstall teagood-nalikoli60

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-nalikoli60 package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your package dependencies for vulnerabilities.

Conclusion

The teagood-nalikoli60 package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package management practices. It is crucial for developers to be vigilant and take immediate action to remove such packages from their projects. Utilizing tools like Vulert can enhance security by providing real-time vulnerability alerts.

See every vulnerability recorded for teagood-nalikoli60 →

Share this vulnerability

FAQ

teagood-nalikoli60 is an npm package involved in a malicious campaign that aims to exploit the npm registry for token rewards.

The malicious code modifies your package.json file, removes private flags, and generates random package names, which can lead to the pollution of the npm registry and compromise your project's integrity.

You should uninstall the package immediately using the command: npm uninstall teagood-nalikoli60.

Regularly audit your dependencies, use trusted packages, and consider employing tools like Vulert to monitor for vulnerabilities in real-time.

Vulert is a tool that monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. You can check if your application is affected by this vulnerability using the Vulert playground without any signup.

How To Fix

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

npm uninstall teagood-nalikoli60

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