Malicious Code Detected in every-time Package: A Critical Security Alert

every-time Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-19990: Malicious code in every-time (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The 'every-time' package is an npm library designed to facilitate the execution of functions at specified intervals. It is commonly used in JavaScript applications to manage timed events. However, this package has been found to contain malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the 'every-time' package, which was introduced in version 0. This code can potentially compromise the security of applications by allowing unauthorized access or manipulation of data. The ramifications include data breaches, unauthorized actions, and potential exploitation of the affected systems.

How To Fix

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

npm uninstall every-time

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, consider removing the 'every-time' package from your project until a secure version is released. You can do this by running the command: 'npm uninstall every-time'. Alternatively, you can implement your own timing functions without relying on this package.

Conclusion

The discovery of malicious code in the 'every-time' package highlights the importance of regularly monitoring and updating dependencies in software projects. By following the recommended steps to fix the vulnerability and utilizing tools like Vulert, developers can enhance the security of their applications.

See every vulnerability recorded for every-time →

Share this vulnerability

FAQ

The 'every-time' package is used to execute functions at specified intervals in JavaScript applications.

You can check if your application is affected by using Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to use the Vulert playground without signing up.

If you cannot update the package right away, consider uninstalling it or implementing your own timing functions as a temporary measure.

More information can be found on the GitHub repository of the 'every-time' package, where the vulnerability details are documented.

Using a package with known vulnerabilities can lead to security breaches, data loss, and unauthorized access to your application and its data.

How To Fix

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

npm uninstall every-time

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