# MAL-2026-13149: Malicious code in dolyame-ui-constants (npm)


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

## What is MAL-2026-13149?

MAL-2026-13149 is a malicious package in dolyame-ui-constants, published on 5 Aug 2026. 

### Official description

On require of the package, index.js loads _support.js which assembles Cloudflare Workers hostnames via split-string concatenation (`["oob-work","er.cf101-adf.workers.d","ev"].join("")`, plus cf102-baf and cf103-070 variants) with a DNS fallback to *.dl.wel1.ru. It downloads a platform-specific binary, writes it to /tmp or %TEMP% under deceptive names (`.cache_<hex>` on Linux/macOS, `dotnet_diag_<hex>.exe` on Windows to mimic a Microsoft diagnostic tool), chmods it 0755, and spawns it detached via `cp.spawn("/bin/sh",["-c",fp+" &"],{detached:true})` (and `spawn("cmd",...)` on Windows). The payload is unsigned, unpinned, and unverified. Environment variables named `DISABLE_TELEMETRY`, `ANALYTICS_OPT_OUT`, and `DO_NOT_TRACK` frame the behavior as telemetry, but the destinations, filename disguises, and execution pattern are dropper mechanics rather than telemetry. A second, larger parallel dropper implementation lives in lib/telemetry.js (base64-decoded buffers, `fs["chmod"+"Sync"]`, split-string `require("child_"+"process")`, `cp.spawn('/bin/sh',['-c',filePath+' &'])`), staged for activation. Installing or requiring this package causes attacker-controlled code to execute on the installer's host.

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

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-13149 is a malicious package: dolyame-ui-constants (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-13149/ (Markdown: https://insights.sbomify.com/MAL-2026-13149/index.md)
```

## Sources

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

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