Critical Malicious Code Vulnerability in tavily-module Package

tavily-module Updated 25 Nov 2025

Summary

24/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-191432: Malicious code in tavily-module (npm). Affects tavily-module versions 1.0.1. 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

The tavily-module is an npm package designed for specific functionalities within JavaScript applications. It is commonly used for various tasks in web development. However, it has recently been compromised, leading to severe security vulnerabilities that can affect any system where it is installed.

Vulnerability Detail

The tavily-module package has been compromised by a malicious payload known as the Sha1-Hulud: The Second Coming NPM worm. This vulnerability allows the worm to steal tokens and credentials, publishing them to GitHub. It can propagate itself to other npm packages owned by the user and establish persistence through GitHub actions. Additionally, there is a risk that the worm may destroy the user's home directory, leading to significant data loss and system compromise.

How To Fix

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

npm uninstall tavily-module

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, it is advised to uninstall the tavily-module package using the command: npm uninstall tavily-module. However, be aware that simply removing the package may not eliminate all malicious software that has been installed as a result of the compromise.

Conclusion

The tavily-module package has been compromised, posing a significant risk to systems where it is installed. Immediate action is required to remove the package and secure any sensitive information. Users are encouraged to utilize tools like Vulert for ongoing monitoring of vulnerabilities.

See every vulnerability recorded for tavily-module →

Share this vulnerability

FAQ

The tavily-module is an npm package used in JavaScript applications for various functionalities, but it has been compromised, leading to security vulnerabilities.

The malicious payload can steal sensitive tokens and credentials, publish them to GitHub, and potentially destroy your home directory.

If you have the tavily-module installed, you should uninstall it immediately and rotate any secrets or keys stored on your computer.

Yes, you can use Vulert to monitor and alert for open-source vulnerabilities in your software. You can check if your application is affected by this vulnerability using the Vulert playground without any signup.

No, uninstalling the tavily-module may not remove all malicious software that has been installed. It is essential to take further security measures.

How To Fix

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

npm uninstall tavily-module

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