# MAL-2026-15586: Malicious code in originaldevelopmentstelemetry (npm)


- **Type:** Malicious package
- **Package:** `originaldevelopmentstelemetry` (npm)
- **Published:** 30 Aug 2026
- **Also known as:** GHSA-m8hq-jrvf-g8xm

## What is MAL-2026-15586?

MAL-2026-15586 is a malicious package in originaldevelopmentstelemetry, published on 30 Aug 2026. 

### Official description

The package is advertised as a telemetry utility but its sole exported function, `downloadAndRunClient`, downloads `updater.hta` from `raw.githubusercontent.com/Acevatex/Testprogram/main/updater.hta` (an unrelated personal GitHub account, on the mutable `main` branch, with no pinning and no hash or signature check), writes it to a temporary path, and launches it via Windows `mshta` as a detached process. HTA execution grants the remote repository owner arbitrary code execution on any Windows host that invokes this function, and the fetched content can change at any time without a new package release. The stated 'telemetry' purpose is inconsistent with a Windows HTA runner, and the author metadata is a generic 'originaldevelopments' identity.

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

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

## Sources

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

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