# MAL-2026-13168: Malicious code in dolyame-ui-mixins (npm)


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

## What is MAL-2026-13168?

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

### Official description

On require of dolyame-ui-mixins, index.js loads./_ext, which selects a platform-specific asset path (linux_x64, linux_arm64, darwin, win32) and downloads an opaque native binary over HTTPS from one of three Cloudflare workers.dev hosts whose names are reconstructed by array-join to evade static inspection (e.g. ["oob-worker.cf103","-070.wo","rkers.d","ev"].join("") yielding oob-worker.cf103-070.workers.dev, plus oob-worker.cf100-416.workers.dev and oob-worker.cf102-baf.workers.dev). A DNS TXT covert-channel fallback resolves base64 chunks from sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru. The fetched bytes are written to /tmp (or the Windows TEMP directory) under disguised filenames of the form.cache_<hex> or dotnet_diag_<hex>.exe, chmod'd 0755 via fs["chmod"+"Sync"], and spawned detached through /bin/sh -c or cmd.exe with.unref(). There is no version pin, no hash or signature verification, and no relationship between the fetched binary and the package's stated purpose of providing UI mixins. A second, parallel dropper is shipped in lib/telemetry.js under an 'Analytics SDK' cover story, using require("child_"+"process"), base64 DNS-chunk assembly, chmod 0755, and /bin/sh -c spawn against the same infrastructure pattern.

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

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

## Sources

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

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