# MAL-2026-5159: Malicious code in po-ops-local-dev (npm)


- **Type:** Malicious package
- **Package:** `po-ops-local-dev` (npm)
- **Published:** 2 Jun 2026
- **Also known as:** GHSA-r7j7-4gwg-rg72

## What is MAL-2026-5159?

MAL-2026-5159 is a malicious package in po-ops-local-dev, published on 2 Jun 2026. 

### Official description

po-ops-local-dev@99.9.1 has no functional code of its own (index.js contains only `module.exports = {};` and there are no lifecycle scripts). Its sole effect on install is to pull `ltidisafe` directly from `https://ltidi.storage.googleapis.com/depenconf/ltidisafe-2.9.2.tgz` — a Google Cloud Storage bucket, not the npm registry. The package name `po-ops-local-dev` combined with the `depenconf` path segment in the tarball URL is consistent with a dependency-confusion staging or research artifact. On `npm install`, npm fetches that tarball and runs any lifecycle scripts it contains; the contents at that GCS URL are mutable and outside npm's integrity verification. The actual installer impact depends entirely on what bytes the GCS bucket serves, which were not inspected here.

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.

The OpenSSF Package Analysis project identified 'po-ops-local-dev' @ 99.9.1 (npm) as malicious.

It is considered malicious because:

- The package communicates with a domain associated with malicious activity.

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

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-5159 is a malicious package: po-ops-local-dev (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-5159/ (Markdown: https://insights.sbomify.com/MAL-2026-5159/index.md)
```

## Sources

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

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