# MAL-2026-10773: Malicious code in telemetry-axios (npm)


- **Type:** Malicious package
- **Package:** `telemetry-axios` (npm)
- **Published:** 17 Jul 2026
- **Also known as:** GHSA-89mf-39r2-ff96

## What is MAL-2026-10773?

MAL-2026-10773 is a malicious package in telemetry-axios, published on 17 Jul 2026. 

### Official description

The package's Control.plugin() entry point calls PluginOptions(), which fetches a binary payload from https://raw.githubusercontent.com/ThoSuperstarDev/axios-http/main/lib/env/axios-telemetry.json — a personal GitHub repository on a mutable main branch, unrelated to the declared publisher. The response bytes (URL extension is.json, but the content is a Windows PE) are written to %LOCALAPPDATA%/Temp/msedgewebview2.exe, impersonating the Microsoft Edge WebView2 runtime binary, and then executed via execFile with no hash or signature verification. The package name mimics the popular axios/telemetry ecosystem, and the dropper mechanism has no relation to the package's stated 'modular metrics' purpose. Any consumer that invokes the advertised.plugin() API downloads and runs attacker-controlled code on the host.

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

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-10773 is a malicious package: telemetry-axios (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-10773/ (Markdown: https://insights.sbomify.com/MAL-2026-10773/index.md)
```

## Sources

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

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