Malicious Code Vulnerability in dns-filter-dashboard Package

dns-filter-dashboard Updated 19 Mar 2026

Summary

18/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1708: Malicious code in dns-filter-dashboard (npm). Affects dns-filter-dashboard versions 99.1.0 – 99.1.1. 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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The dns-filter-dashboard package is a Node.js application designed for managing DNS filtering services. It provides users with a dashboard interface to configure and monitor DNS filtering settings. However, this package has been identified as containing malicious code, which poses a significant security risk to its users.

Vulnerability Detail

The vulnerability in the dns-filter-dashboard package arises from the inclusion of malicious code that can compromise the security of applications utilizing this package. This code can lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The malicious code was introduced in versions 99.1.0 and 99.1.1, as identified by ReversingLabs.

How To Fix

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

npm uninstall dns-filter-dashboard

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 dns-filter-dashboard package from their project until a secure version is confirmed. This can be done using the command: npm uninstall dns-filter-dashboard.

Conclusion

The dns-filter-dashboard package has been identified to contain malicious code, posing a serious security threat. Users are advised to update to a secure version or remove the package until a fix is available. Monitoring tools like Vulert can help keep applications secure.

See every vulnerability recorded for dns-filter-dashboard →

Share this vulnerability

FAQ

The dns-filter-dashboard package is a Node.js application that allows users to manage DNS filtering services through a dashboard interface.

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

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

Versions 99.1.0 and 99.1.1 of the dns-filter-dashboard package are known to contain the malicious code.

Using Vulert, you can monitor and receive alerts for open-source vulnerabilities in your software by simply using the package-lock.json file.

How To Fix

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

npm uninstall dns-filter-dashboard

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