Which versions of dolyame-ui-filter are malicious?

The following npm versions of dolyame-ui-filter are flagged malicious: 35.5.3. Treat any of these as compromised.

How do I remediate dolyame-ui-filter if I installed it?

dolyame-ui-filter is a typosquat — you almost certainly intended a legitimately-named package. Remove dolyame-ui-filter, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed dolyame-ui-filter — how do I know if it already compromised me?

If dolyame-ui-filter was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is dolyame-ui-filter part of a known attack campaign?

Yes — dolyame-ui-filter is associated with the IN-MAL-2026-015622 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 dolyame-ui-filter across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for dolyame-ui-filter (version 35.5.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dolyame-ui-filter across your stack and pipelines.

Malicious package

dolyame-ui-filternpm

dolyame-ui-filter is a confirmed malicious npm package (MAL-2026-13154) that typosquats a legitimate package to trick installs (malicious version 35.5.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dolyame-ui-filter (npm)

MAL-2026-13154

Immediate action

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

npm uninstall dolyame-ui-filter

What this malware does

[email protected] is advertised as a UI toolkit but its main entry loads platform.js, which on require assembles destination hostnames at runtime via array.join('') to hide them from static inspection, resolving to Cloudflare Worker endpoints oob-worker.cf101-a.df.workers.dev, oob-worker.cf100-416.workers.dev, and oob-worker.cf99-9b3.workers.dev, with a DNS TXT fallback that reads chunked base64 from sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru. The module downloads a platform-specific binary via https.get, writes it to a temp path under a decoy name (dotnet_diag<hex>.exe on Windows,.cache_<hex> on Unix), chmods 0755, and spawns it detached via cmd.exe or /bin/sh -c with unref(). Comments in the file mislabel the flow as telemetry/session dedup while the actual operation fetches and executes an opaque binary from an anonymous host. The delivery signals (anonymous Cloudflare Worker infrastructure with runtime-assembled hostnames, DNS TXT covert channel, decoy filenames impersonating.NET diagnostic tooling, detached background execution, purpose mismatch with the advertised UI package) satisfy the dropper fingerprint.

Malicious versions

1 flagged

35.5.3

Indicators of compromise (SHA-256)

171758619b11932bfa2790206d34ea6322b3985c9cfe083915c41fdb5b18f9ed

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for dolyame-ui-filter (version 35.5.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dolyame-ui-filter across your stack and pipelines.
If you installed it — respond
dolyame-ui-filter is a typosquat — you almost certainly intended a legitimately-named package. Remove dolyame-ui-filter, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If dolyame-ui-filter was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks dolyame-ui-filter before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. dolyame-ui-filter on npm has been identified as a malicious package (version 35.5.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015622

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks dolyame-ui-filter-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