# MAL-2026-5348: Malicious code in os-ulid-void (npm)


- **Type:** Malicious package
- **Package:** `os-ulid-void` (npm)
- **Published:** 9 Jun 2026
- **Also known as:** GHSA-7fhf-p3wv-2xrc

## What is MAL-2026-5348?

MAL-2026-5348 is a malicious package in os-ulid-void, published on 9 Jun 2026. 

### Official description

The package ships a minified file at dist/payload.js where multiple HTTP POST call sites appear (lines 14503, 14532, 14716, 14834, 15716). The literal evidence captured is only the keyword 'POST' without surrounding context, so the destinations, request bodies, and reachability (install-time vs import-time vs explicit user-call) cannot be determined from the available signals. The package name resembles common ULID utility naming and may be a confusion candidate, but no concrete installer-harm code path (env-var scrape, credential read, hardcoded attacker endpoint, dropper, lifecycle hook tied to an exfil call) has been verified. Manual review of dist/payload.js is recommended to confirm whether the POST sites target attacker-controlled destinations or are part of legitimate API surface.

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

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

## Sources

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

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