Malicious Code Detected in date-echo-xvcv Package - Immediate Action Required

date-echo-xvcv Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-18026: Malicious code in date-echo-xvcv (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 date-echo-xvcv package is an npm library designed for date manipulation and formatting. It is utilized in various JavaScript applications to handle date-related functionalities efficiently. However, this package has been found to contain malicious code that poses a significant security risk to applications that depend on it.

Vulnerability Detail

The vulnerability in the date-echo-xvcv package originates from the inclusion 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 affects all versions starting from 0, making it critical for developers to take immediate action to mitigate potential risks.

How To Fix

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

npm uninstall date-echo-xvcv

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 date-echo-xvcv package altogether and implement alternative date handling methods using native JavaScript Date objects or other trusted libraries such as moment.js or date-fns.

Conclusion

The discovery of malicious code in the date-echo-xvcv package highlights the importance of maintaining secure dependencies in software development. Developers are urged to take immediate action to remove this package and monitor their applications for vulnerabilities.

See every vulnerability recorded for date-echo-xvcv →

Share this vulnerability

FAQ

The date-echo-xvcv package is an npm library used for date manipulation and formatting in JavaScript applications.

The malicious code can lead to unauthorized access and data breaches, posing a serious security threat to applications that utilize this package.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application using the Vulert playground at Vulert Scanner.

Currently, there is no patched version available. It is recommended to remove the package and use a secure alternative.

Remove the date-echo-xvcv package from your project immediately and consider using alternative libraries for date handling.

How To Fix

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

npm uninstall date-echo-xvcv

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