Which versions of dnsfilter-frontend are malicious?

The following npm versions of dnsfilter-frontend are flagged malicious: 99.1.0. Treat any of these as compromised.

How do I remediate dnsfilter-frontend if I installed it?

Remove dnsfilter-frontend 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 dnsfilter-frontend — how do I know if it already compromised me?

If dnsfilter-frontend 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 dnsfilter-frontend part of a known attack campaign?

Yes — dnsfilter-frontend is associated with the RLMA-2026-01246 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 dnsfilter-frontend across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for dnsfilter-frontend (version 99.1.0).

Malicious package

dnsfilter-frontendnpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

dnsfilter-frontend is a confirmed malicious npm package (MAL-2026-1709) that executes malicious code on install (malicious version 99.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dnsfilter-frontend (npm)

MAL-2026-1709

Immediate action

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

npm uninstall dnsfilter-frontend

What this malware does

The package dnsfilter-frontend was found to contain malicious code.

Malicious versions

1 flagged

99.1.0

Indicators of compromise (SHA-256)

a32016944148dc098efbb5022fd1f3b5619daf9b7a05676c3b3b95796a1d8e9f

f3fbe7b6607030de1223e6c9beb7c21f7c5bafbbf72cdceb41d8eee9105b6e3e

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for dnsfilter-frontend (version 99.1.0).
If you installed it — respond
Remove dnsfilter-frontend 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 dnsfilter-frontend 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. dnsfilter-frontend on npm has been identified as a malicious package (version 99.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-01246

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks dnsfilter-frontend-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