Critical Malicious Code Vulnerability in ddos-l7 Package

ddos-l7 Updated 02 Dec 2025

Summary

02/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-191547: Malicious code in ddos-l7 (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 ddos-l7 package is an npm module designed for managing Layer 7 Distributed Denial of Service (DDoS) attacks. It provides functionalities to help developers mitigate such attacks in their applications. However, this package has been compromised, embedding malicious code that poses severe security risks to any system using it.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the ddos-l7 package. This code can fully compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The implications of this vulnerability are significant, as it can lead to data breaches and loss of control over the affected systems. Users are advised to treat any system running this package as compromised.

How To Fix

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

npm uninstall ddos-l7

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

There are no effective workarounds for this vulnerability. The only recommended action is to uninstall the ddos-l7 package and secure your system.

Conclusion

The ddos-l7 package has been found to contain malicious code that compromises the security of any system using it. Immediate action is required to uninstall the package and secure any sensitive information. Regular monitoring of dependencies is recommended to prevent future vulnerabilities.

See every vulnerability recorded for ddos-l7 →

Share this vulnerability

FAQ

You should uninstall the ddos-l7 package immediately and rotate any secrets or keys stored on the affected system.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

Failing to address this vulnerability can lead to unauthorized access to sensitive data and complete control of your system by malicious actors.

No, there is no patched version available for the ddos-l7 package. The only solution is to remove it entirely.

While most npm packages are safe, it is essential to regularly monitor and audit your dependencies for vulnerabilities using tools like Vulert.

How To Fix

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

npm uninstall ddos-l7

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