Malicious Code Detected in frantic-time-thread Package

frantic-time-thread Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-20932: Malicious code in frantic-time-thread (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

The frantic-time-thread package is an npm library designed for managing time-based threading operations in JavaScript applications. It offers features that allow developers to execute tasks at specified intervals, making it a useful tool for asynchronous programming. However, this package has been identified to contain malicious code, posing significant risks to applications that utilize it.

Vulnerability Detail

The vulnerability in the frantic-time-thread package arises from the presence of malicious code that can compromise the security of applications using this library. This code can lead to unauthorized access, data breaches, or other malicious activities. The issue was introduced in version 0 and affects all subsequent versions, making it critical for developers to address this vulnerability promptly.

How To Fix

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

npm uninstall frantic-time-thread

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, you can avoid using the frantic-time-thread package altogether and implement your own time management functionality using native JavaScript features such as setTimeout and setInterval. For example:

const myTask = () => {
  console.log('Task executed');
};

setInterval(myTask, 1000);

// Executes myTask every second

Conclusion

The frantic-time-thread package has been identified as containing malicious code that poses a significant security risk. Developers are urged to remove this package and consider alternatives to safeguard their applications. Regularly monitoring for vulnerabilities using tools like Vulert can help maintain application security.

See every vulnerability recorded for frantic-time-thread →

Share this vulnerability

FAQ

frantic-time-thread is an npm package used for managing time-based threading operations in JavaScript applications.

The malicious code can lead to unauthorized access and potential data breaches in applications that use the package.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without signup.

You should remove the package from your project and consider using a secure alternative or implement your own time management functionality.

Currently, there is no patched version available for the frantic-time-thread package. It is advised to remove it from your project.

How To Fix

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

npm uninstall frantic-time-thread

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