Malicious Code Detected in cronemod Package - Security Alert

cronemod Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-17694: Malicious code in cronemod (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 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 cronemod package is an npm library designed for scheduling tasks in JavaScript applications. It provides developers with a straightforward way to execute functions at specified intervals. However, recent findings have revealed that this package contains malicious code, posing significant risks to applications that utilize it.

Vulnerability Detail

The vulnerability in the cronemod package stems from the inclusion of malicious code that can compromise the security of applications using it. This code may lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to take immediate action.

How To Fix

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

npm uninstall cronemod

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 cronemod package from your project until a secure version is available. You can do this by executing the command: 'npm uninstall cronemod'. This will help mitigate the risk of exploitation while you await a fix.

Conclusion

The discovery of malicious code in the cronemod package poses a serious threat to applications that rely on it. Users are urged to take immediate action by updating or removing the package until a secure version is available. Continuous monitoring for vulnerabilities is essential to maintain application security.

See every vulnerability recorded for cronemod →

Share this vulnerability

FAQ

The cronemod package is used for scheduling tasks in JavaScript applications, allowing developers to run functions at specified intervals.

The malicious code was identified by security researchers from Amazon Inspector, who reported the findings to the community.

Using the compromised package can lead to unauthorized access, data breaches, and other harmful actions within your application.

Yes, you can use Vulert to monitor and alert you in real-time for open-source vulnerabilities in your software. It requires only the package-lock.json file.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

How To Fix

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

npm uninstall cronemod

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