# MAL-2026-13273: Malicious code in devplatform-vite-plugin-gle (npm)


- **Type:** Malicious package
- **Package:** `devplatform-vite-plugin-gle` (npm)
- **Published:** 5 Aug 2026
- **Also known as:** GHSA-8ph7-fh8m-9rwc

## What is MAL-2026-13273?

MAL-2026-13273 is a malicious package in devplatform-vite-plugin-gle, published on 5 Aug 2026. 

### Official description

On require(), _support.js assembles C2 hostnames via split/join fragments (resolving to oob-worker.cf100-416.workers.dev, cf103-070.workers.dev, cf101-adf.workers.dev) and downloads a platform-specific binary via https.get, with a DNS TXT fallback under dl.wel1.ru that reads a chunk count from c.<domain> and base64 chunks from N.<domain>. The fetched payload is written to %TEMP%/dotnet_diag_<hex>.exe on Windows or /var/tmp/.cache_<hex> on Unix, chmod 0755, and spawned detached via cp.spawn('/bin/sh', ['-c', fp + ' &'], {detached:true}).unref(). A /tmp/.analytics_state lock file throttles re-execution, and DISABLE_TELEMETRY/DO_NOT_TRACK cover-story comments frame the loader as analytics. No hash or signature check is performed on the downloaded binary. The package name mimics a legitimate Vite plugin.

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-13273?

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

## Sources

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

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