# MAL-2026-13557: Malicious code in dolyame-ui-checkablegroup (npm)


- **Type:** Malicious package
- **Package:** `dolyame-ui-checkablegroup` (npm)
- **Published:** 7 Aug 2026

## What is MAL-2026-13557?

MAL-2026-13557 is a malicious package in dolyame-ui-checkablegroup, published on 7 Aug 2026. 

### Official description

The package presents itself as a UI checkable-group helper but on require executes a dropper. `_helpers.js` and the main-exported `lib/telemetry.js` assemble destination hostnames at runtime from split-string arrays (e.g. `["oob-worker.cf1","00-416.work","er","s.dev"].join("")` yielding `oob-worker.cf100-416.workers.dev`, plus `cf101-adf` and `cf103-070` siblings), select a platform-specific endpoint, download an opaque binary via `https.get`, write it to `/tmp` or `%TEMP%` under a spoofed name mimicking a Microsoft diagnostic tool (`dotnet_diag_<hex>.exe`, `.cache_<hex>`), `chmodSync` 0755, and spawn it detached via `cp.spawn("/bin/sh",["-c", filePath+" &"], {detached:true})` on Unix or `cmd.exe /c start /b` on Windows. A covert DNS-TXT fallback channel under `*.dl.wel1.ru` reassembles a base64 payload from numbered subdomains (`c.<domain>` for count, `<i>.<domain>` for chunks). No hash or signature verification is performed. The dropper is duplicated across `_helpers.js` and the main-exported `lib/telemetry.js`, ensuring execution on any `require` of the package. Hostname obfuscation via split-string concatenation, spoofed on-disk names, detached execution, and the DNS-TXT covert channel are consistent with purpose-built malware distributed as a UI-helper lure.

## What should I do about MAL-2026-13557?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-13557 is a malicious package: dolyame-ui-checkablegroup (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-13557/ (Markdown: https://insights.sbomify.com/MAL-2026-13557/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-13557

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-13557/
Summaries are generated and may contain mistakes; the official description above is the record.