# MAL-2026-13571: Malicious code in dolyame-ui-generateid (npm)


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

## What is MAL-2026-13571?

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

### Official description

On require() of the package, index.js loads _shim.js which selects a platform-specific payload URL by concatenating string fragments to reconstruct hostnames oob-worker.cf103-070.workers.dev, oob-worker.cf99-9b3.workers.dev, and oob-worker.cf102-baf.workers.dev, with a covert DNS TXT-record fallback that reads chunk counts from c.<domain> and base64 payload fragments from N.<domain> under sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru. The fetched binary is written to /var/tmp or %TEMP% under disguised names such as.cache_<rand> or dotnet_diag_<rand>.exe, chmodded 0755 on POSIX, and spawned detached via /bin/sh -c "<path> &" or cmd.exe /c start. A second import-reachable dropper path exists in lib/telemetry.js: it decodes base64 chunks into a Buffer, invokes fs["chmod"+"Sync"] with mode 0o755, and calls cp.spawn("/bin/sh", ["-c", filePath+" &"]). Anti-analysis techniques include split-string require("child_"+"process"), split-property fs["chmod"+"Sync"], array-join hostname assembly, and DNS TXT-record staged payload delivery. The package's stated purpose (a UI ID-generation helper / observability SDK) does not require fetching and executing native binaries from anonymous Cloudflare Workers domains.

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

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

## Sources

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

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