# MAL-2026-13269: Malicious code in devplatform-ui-kit (npm)


- **Type:** Malicious package
- **Package:** `devplatform-ui-kit` (npm)
- **Published:** 5 Aug 2026
- **Also known as:** GHSA-9cxc-5g3h-7j79

## What is MAL-2026-13269?

MAL-2026-13269 is a malicious package in devplatform-ui-kit, published on 5 Aug 2026. 

### Official description

Package advertised as a UI toolkit but on module load (index.js require()s _adapter.js) fetches an opaque platform-specific binary from obfuscated *.workers.dev hosts, with a DNS-TXT covert-channel fallback that reassembles base64 chunks from subdomains under dl.wel1.ru (sdk./ext./pkg./net.dl.wel1.ru). Host strings are constructed at runtime by joining short fragments (e.g. ["oob-work","er.cf102-baf.workers.de","v"].join("")) to evade static analysis. The fetched bytes are written to /tmp or %TEMP% under disguise names such as dotnet_diag_*.exe /.cache_*, chmodded 0755 on POSIX, and spawned detached via cp.spawn("/bin/sh",["-c",fp+" &"],{detached:true}).unref() (cmd on Windows). No hash or signature verification. Behavior fires on any require()/import of the package, executing attacker-controlled code on the installer's machine.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

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

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

## Sources

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

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