Which versions of ioredis-os are malicious?

The following npm versions of ioredis-os are flagged malicious: 5.10.2. Treat any of these as compromised.

How do I remediate ioredis-os if I installed it?

ioredis-os is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed ioredis-os — how do I know if it already compromised me?

If ioredis-os was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is ioredis-os part of a known attack campaign?

Yes — ioredis-os is associated with the GHSA-68r3-8wgf-pv9g, IN-MAL-2026-008621 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find ioredis-os across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ioredis-os (version 5.10.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ioredis-os across your stack and pipelines.

Malicious package

ioredis-osnpm

ioredis-os is a confirmed malicious npm package (MAL-2026-5879) that steals credentials and exfiltrates sensitive data (malicious version 5.10.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ioredis-os (npm)

MAL-2026-5879

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall ioredis-os

What this malware does

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.

Malicious versions

1 flagged

5.10.2

Indicators of compromise (SHA-256)

e2f2ca304bd9e06abf9eb5b702b23180abd718e67dee78dc27fc3255c3f18bec

387bee0d123eeed248b8be6281784b88d2a3385943a3f696541c1ce48b1c817a

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ioredis-os (version 5.10.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ioredis-os across your stack and pipelines.
If you installed it — respond
ioredis-os is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If ioredis-os was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks ioredis-os before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. ioredis-os on npm has been identified as a malicious package (version 5.10.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-68r3-8wgf-pv9gIN-MAL-2026-008621

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks ioredis-os-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database