What does the dolyame-ui-checkbox malware do?

On require of the package, index.js loads _vendor.js, which reconstructs a set of C2 hostnames from string-split fragments (four *.workers.dev mirrors and a *.dl.wel1.ru DNS-TXT fallback), selects a per-platform endpoint, downloads an attacker-controlled binary via https.get (or reassembles it from chunked base64 DNS TXT records at c. / . when HTTPS is blocked), writes it to /var/tmp on Unix or %TEMP% on Windows under cover-story names such as.cache_ or dotnet_diag_ .exe, chmods 0755, and spawns it detached via /bin/sh -c or cmd.exe /c start /b. A second, functionally equivalent dropper is packaged as lib/telemetry.js (81 KB), disguised as an analytics SDK, implemen

Which versions of dolyame-ui-checkbox are malicious?

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

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

dolyame-ui-checkbox establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

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

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

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

Malicious package

dolyame-ui-checkboxnpm

dolyame-ui-checkbox is a confirmed malicious npm package (MAL-2026-13144) that opens a backdoor for remote access (malicious version 35.6.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dolyame-ui-checkbox (npm)

MAL-2026-13144

Immediate action

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

npm uninstall dolyame-ui-checkbox

What this malware does

On require of the package, index.js loads vendor.js, which reconstructs a set of C2 hostnames from string-split fragments (four *.workers.dev mirrors and a *.dl.wel1.ru DNS-TXT fallback), selects a per-platform endpoint, downloads an attacker-controlled binary via https.get (or reassembles it from chunked base64 DNS TXT records at c.<domain>/<i>.<domain> when HTTPS is blocked), writes it to /var/tmp on Unix or %TEMP% on Windows under cover-story names such as.cache<hex> or dotnet_diag_<hex>.exe, chmods 0755, and spawns it detached via /bin/sh -c or cmd.exe /c start /b. A second, functionally equivalent dropper is packaged as lib/telemetry.js (81 KB), disguised as an analytics SDK, implementing the same fetch->chmod 755->spawn('/bin/sh','-c', path+' &') pattern with a base64-decoded payload path. Host reconstruction via string-splitting and the DNS-TXT covert transport are anti-analysis features paired with the dropper.

Malicious versions

1 flagged

35.6.9

Indicators of compromise (SHA-256)

2a445ffd0f222f7d58ad870ad641f9dd2fb21a1cc43795cbef5c58109cafebbe

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for dolyame-ui-checkbox (version 35.6.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dolyame-ui-checkbox across your stack and pipelines.
If you installed it — respond
dolyame-ui-checkbox establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If dolyame-ui-checkbox 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-checkbox 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-checkbox on npm has been identified as a malicious package (version 35.6.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015631

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks dolyame-ui-checkbox-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database