Which versions of dns-filter-dashboard are malicious?

The following npm versions of dns-filter-dashboard are flagged malicious: 99.1.0, 99.1.1. Treat any of these as compromised.

How do I remediate dns-filter-dashboard if I installed it?

Remove dns-filter-dashboard from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed dns-filter-dashboard — how do I know if it already compromised me?

If dns-filter-dashboard was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is dns-filter-dashboard part of a known attack campaign?

Yes — dns-filter-dashboard is associated with the RLMA-2026-01245 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find dns-filter-dashboard across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for dns-filter-dashboard (2 malicious versions).

Malicious package

dns-filter-dashboardnpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

dns-filter-dashboard is a confirmed malicious npm package (MAL-2026-1708) that executes malicious code on install (malicious versions 99.1.0, 99.1.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dns-filter-dashboard (npm)

MAL-2026-1708

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall dns-filter-dashboard

What this malware does

The package dns-filter-dashboard was found to contain malicious code.

Malicious versions

2 flagged

99.1.099.1.1

Indicators of compromise (SHA-256)

7588dbf7198ee4a89cf9b2589dd3fad5dd6d982c4a5cd17a5e8c830e57827372

98ebb64805440d479f71a2a6243b11ebb3a56b53dacce612b516ab01acb3df87

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for dns-filter-dashboard (2 malicious versions).
If you installed it — respond
Remove dns-filter-dashboard from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If dns-filter-dashboard was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. dns-filter-dashboard on npm has been identified as a malicious package (versions 99.1.0, 99.1.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-01245

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks dns-filter-dashboard-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database