Critical Malicious Code Vulnerability in timeout-ts Package

timeout-ts Updated 08 Jan 2026

Summary

08/01/2026
CRITICAL
No i
Critical
Not published

MAL-2026-158: Malicious code in timeout-ts (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The timeout-ts package is an npm library designed to provide a simple way to manage timeouts in JavaScript applications. It offers features such as setting and clearing timeouts, making it easier for developers to handle asynchronous operations. However, this package has been compromised, leading to severe security risks for any application that utilizes it.

Vulnerability Detail

The vulnerability stems from malicious code embedded within the timeout-ts package. This code can fully compromise any computer that has the package installed or running, allowing unauthorized access to sensitive information such as secrets and keys. The origin of this vulnerability is linked to a malicious actor who has inserted harmful code into the package, which is classified under CWE-506, indicating the presence of embedded malicious code. The ramifications of this vulnerability are dire, as it can lead to data breaches and loss of control over the affected systems.

How To Fix

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

npm uninstall timeout-ts

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, you can temporarily replace the functionality provided by timeout-ts with native JavaScript timeout functions, such as setTimeout and clearTimeout, until a secure alternative is identified.

Conclusion

The timeout-ts package has been compromised with malicious code, posing significant risks to any system that utilizes it. Immediate action is necessary to remove the package and secure sensitive information. Users are encouraged to monitor their applications for vulnerabilities using tools like Vulert.

See every vulnerability recorded for timeout-ts →

Share this vulnerability

FAQ

timeout-ts is an npm package that simplifies the management of timeouts in JavaScript applications.

The malicious code can compromise your system, allowing unauthorized access to sensitive information and potentially leading to data breaches.

You should immediately remove the timeout-ts package and rotate any secrets or keys stored on the affected system.

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

While removing the package is critical, there is no guarantee that all malicious software will be removed. It is essential to take additional security measures.

How To Fix

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

npm uninstall timeout-ts

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