# MAL-2026-5879: Malicious code in ioredis-os (npm)


- **Type:** Malicious package
- **Package:** `ioredis-os` (npm)
- **Published:** 16 Jun 2026
- **Also known as:** GHSA-68r3-8wgf-pv9g

## What is MAL-2026-5879?

MAL-2026-5879 is a malicious package in ioredis-os, published on 16 Jun 2026. 

### Official description

`ioredis-os` appends `-os` to the widely-used `ioredis` package name and ships what appears to be a verbatim fork of ioredis (same author, same upstream repository URL `git://github.com/luin/ioredis.git`, identical API surface). It also declares a dependency on `redis-type-os`, another `-os`-suffixed name that mirrors `redis-type`. No install lifecycle scripts are declared and no credential theft, exfiltration, dropper, or silent-relay behavior is present in the reachable code from `built/index.js` — the current code looks clean. The concern is the naming pattern: a developer who mistypes or otherwise reaches `ioredis-os` instead of `ioredis` ends up running a fork that the upstream maintainer does not control, and the chained `-os` dependency expands that surface. Routing to human review so a maintainer can assess whether the fork is legitimate (intended derivative) or a name-confusion squat that should be removed.

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

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

## Sources

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

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