Malicious Code Detected in date-dr3-project Package

date-dr3-project Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-18024: Malicious code in date-dr3-project (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 date-dr3-project is an npm package that is utilized for various date manipulation tasks in JavaScript applications. It is designed to simplify date formatting, parsing, and calculations. However, recent findings have revealed that this package contains malicious code, which poses a significant risk to users and their applications.

Vulnerability Detail

The vulnerability stems from the inclusion of malicious code within the date-dr3-project package. This code can potentially compromise the security of applications that utilize this package, leading 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 users to take immediate action.

How To Fix

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

npm uninstall date-dr3-project

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 avoid using the date-dr3-project package and implement alternative date manipulation libraries such as 'date-fns' or 'moment.js'. For example, to install date-fns, use the command: npm install date-fns.

Conclusion

The date-dr3-project package has been identified as containing malicious code, posing a significant risk to users. Immediate action is required to remove the package and replace it with a secure alternative to ensure the safety of applications.

See every vulnerability recorded for date-dr3-project →

Share this vulnerability

FAQ

The date-dr3-project package is an npm library designed for date manipulation 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 if your application is affected without needing to sign up.

It is crucial to uninstall the date-dr3-project package immediately and replace it with a secure alternative.

Currently, there is no patched version available for the date-dr3-project package. It is recommended to uninstall it.

How To Fix

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

npm uninstall date-dr3-project

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