Malicious Code Detected in date-g9g-project Package - Security Alert

date-g9g-project Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-18030: Malicious code in date-g9g-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 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-g9g-project is an npm package designed for date manipulation and formatting. It is widely used in JavaScript applications for handling date-related functionalities. However, recent findings have revealed that this package contains malicious code, posing a significant security risk to applications that rely on it.

Vulnerability Detail

The vulnerability stems from the inclusion of malicious code within the date-g9g-project package. This code can potentially compromise the security of applications using the package, leading to unauthorized access, data breaches, or other malicious activities. The issue was introduced in version 0 and affects all subsequent versions. Users of this package should be aware of the risks associated with its use and take immediate action to mitigate potential threats.

How To Fix

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

npm uninstall date-g9g-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, consider replacing the date-g9g-project package with an alternative date manipulation library that does not have known vulnerabilities. Libraries such as 'date-fns' or 'moment.js' can be used as substitutes.

Conclusion

The discovery of malicious code in the date-g9g-project package poses a serious threat to applications that utilize it. Immediate action is required to remove the package and consider alternatives to safeguard your application from potential security breaches.

See every vulnerability recorded for date-g9g-project →

Share this vulnerability

FAQ

The date-g9g-project is an npm package used for date manipulation and formatting in JavaScript applications.

The malicious code can lead to unauthorized access and potential data breaches in applications that utilize the package.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.

Currently, there is no patched version available. It is recommended to remove the package until a secure version is released.

Consider using alternative libraries for date manipulation, such as 'date-fns' or 'moment.js', until the vulnerability is resolved.

How To Fix

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

npm uninstall date-g9g-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