Malicious Code Detected in Doomclock Package - Security Alert

doomclock Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-18643: Malicious code in doomclock (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

Doomclock is an npm package designed for managing countdown timers and alarms in JavaScript applications. It is widely used for its simplicity and ease of integration into various projects. However, recent findings have revealed that the package contains malicious code, posing a significant risk to users who have integrated it into their applications.

Vulnerability Detail

The vulnerability in the doomclock package originates from the inclusion of malicious code that can compromise the security of applications utilizing this package. This malicious code may lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The issue is particularly concerning as it affects all versions starting from the initial release, making it imperative 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 doomclock

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, users can remove the doomclock package from their projects until a secure version is released. This can be done by executing the following command: npm uninstall doomclock. Alternatively, consider using a different package that offers similar functionality without the security risks.

Conclusion

The discovery of malicious code in the doomclock package poses a serious threat to users and their applications. It is crucial to take immediate action by updating or removing the package to mitigate any potential risks. Stay informed about vulnerabilities and utilize tools like Vulert to monitor your projects effectively.

See every vulnerability recorded for doomclock →

Share this vulnerability

FAQ

Doomclock is an npm package used for creating countdown timers and alarms in JavaScript applications.

The malicious code can potentially allow unauthorized access and compromise the security of applications using the package.

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

If immediate updates are not possible, consider uninstalling the package and using an alternative solution until a secure version is available.

How To Fix

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

npm uninstall doomclock

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