Malicious Code Vulnerability in tldriver Package

tldriver Updated 22 Sep 2026

Summary

22/09/2026
CRITICAL
No i
Critical
Not published

MAL-2026-16384: Malicious code in tldriver (npm). Affects tldriver versions 0.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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The tldriver package, available on npm, is purportedly designed to interface with Google APIs, including Google Drive, Calendar, and Maps. However, its actual implementation is misleading, as it contains obfuscated scripts that execute potentially harmful code upon installation. The package's integrity is compromised by the presence of these scripts, which are designed to fetch and execute arbitrary code from an external source.

Vulnerability Detail

The vulnerability originates from the tldriver package version 0.0.1, which includes heavily obfuscated preinstall and postinstall scripts. These scripts perform an HTTPS GET request to an anonymous third-party image host, download executable files, and execute them on the user's machine. This behavior poses significant security risks, as it allows the operator of the external host to deliver malicious code at any time, compromising the user's system and data integrity.

How To Fix

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

npm uninstall tldriver

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, avoid using the tldriver package altogether and consider using alternative packages that provide similar functionality without the associated risks. Always review package dependencies and their scripts before installation.

Conclusion

The tldriver package contains a serious vulnerability due to the presence of malicious code in its installation scripts. Users are advised to uninstall the package immediately and seek alternatives to ensure the security of their systems. Regular monitoring for vulnerabilities using tools like Vulert can help maintain software integrity.

See every vulnerability recorded for tldriver →

Share this vulnerability

FAQ

The tldriver package is an npm package that claims to provide access to Google APIs, but it has been found to contain malicious code.

The vulnerability allows the execution of arbitrary code from an external source, which can compromise your system's security and data.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.

If you have installed tldriver, immediately uninstall it using 'npm uninstall tldriver' and consider using alternative packages.

Yes, consider using well-reviewed and maintained packages that provide similar functionality without the risks associated with tldriver.

How To Fix

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

npm uninstall tldriver

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