What does the dolyame-ui-contenteditable malware do?

On require() of the package, index.js unconditionally loads./_compat.js, which reassembles three attacker-controlled Cloudflare Workers hostnames (oob-worker.cf101-adf.workers.dev family) from split string literals, selects an OS/arch-specific remote path, downloads a binary, writes it to /tmp or %TEMP% under disguised names (e.g. dotnet_diag_ .exe,.cache_ ), chmods 0755 on POSIX, and spawns it detached via /bin/sh -c or cmd. A DNS-TXT-record chunked-base64 fallback channel under c. and numeric subdomains of *.dl.wel1.ru (sdk.dl.wel1.ru) reassembles the binary bytes from TXT records when HTTPS egress is blocked. A second parallel dropper in lib/telemetry.js (reached via index

Which versions of dolyame-ui-contenteditable are malicious?

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

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

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

If dolyame-ui-contenteditable 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-contenteditable part of a known attack campaign?

Yes — dolyame-ui-contenteditable is associated with the IN-MAL-2026-016971 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-contenteditable 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-contenteditable (version 35.8.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dolyame-ui-contenteditable across your stack and pipelines.

Malicious package

dolyame-ui-contenteditablenpm

dolyame-ui-contenteditable is a confirmed malicious npm package (MAL-2026-13560) that executes malicious code on install (malicious version 35.8.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dolyame-ui-contenteditable (npm)

MAL-2026-13560

Immediate action

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

npm uninstall dolyame-ui-contenteditable

What this malware does

On require() of the package, index.js unconditionally loads./compat.js, which reassembles three attacker-controlled Cloudflare Workers hostnames (oob-worker.cf101-adf.workers.dev family) from split string literals, selects an OS/arch-specific remote path, downloads a binary, writes it to /tmp or %TEMP% under disguised names (e.g. dotnet_diag<hex>.exe,.cache_<hex>), chmods 0755 on POSIX, and spawns it detached via /bin/sh -c or cmd. A DNS-TXT-record chunked-base64 fallback channel under c.<domain> and numeric subdomains of *.dl.wel1.ru (sdk.dl.wel1.ru) reassembles the binary bytes from TXT records when HTTPS egress is blocked. A second parallel dropper in lib/telemetry.js (reached via index.js exporting require('./lib/telemetry')) uses string-concatenated API names ('child_'+'process', 'chmod'+'Sync') to base64-decode chunks, write to an extension path, chmod 0755, and spawn /bin/sh -c under an Analytics SDK/telemetry cover story. No version pinning, no hash verification, opt-out env checks and a TTL stamp file provide anti-analysis cover.

Malicious versions

1 flagged

35.8.1

Indicators of compromise (SHA-256)

9eaf7524b69f412cf3ba4a466c4b9ade04fcaafd989fd3ff0d437e0a3ec941d0

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for dolyame-ui-contenteditable (version 35.8.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dolyame-ui-contenteditable across your stack and pipelines.
If you installed it — respond
Remove dolyame-ui-contenteditable 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 dolyame-ui-contenteditable 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-contenteditable 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-contenteditable on npm has been identified as a malicious package (version 35.8.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-016971

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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