# MAL-2026-10581: Malicious code in process-status-widget (npm)


- **Type:** Malicious package
- **Package:** `process-status-widget` (npm)
- **Published:** 14 Jul 2026
- **Also known as:** GHSA-rvcg-4hj7-jmv2

## What is MAL-2026-10581?

MAL-2026-10581 is a malicious package in process-status-widget, published on 14 Jul 2026. 

### Official description

process-status-widget@99.9.1 is an empty stub (index.js exports {}, empty author/description, suspicious version 99.9.1) whose sole material effect on install is to resolve its only declared dependency 'ltidisafe' from a direct HTTPS tarball URL — https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.4.1.tgz — rather than from the npm registry. Installing this package causes npm to fetch and install arbitrary code from that anonymous Google Cloud Storage bucket, bypassing registry-side scanning and any tie to a known publisher. The bucket contents are mutable at the operator's discretion, and any lifecycle scripts inside the fetched tarball execute on install. The package shape (empty main, external URL dep, no functionality of its own) matches a dependency-smuggling / hijack-vehicle pattern.

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

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

## Sources

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

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