ioredis-ormnpm
Advisory published Updated
ioredis-orm is a confirmed malicious npm package (MAL-2026-5675) that steals credentials and exfiltrates sensitive data (malicious version 5.11.2). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in ioredis-orm (npm)
What this malware does
The tarball ships a verbatim copy of the legitimate ioredis Redis client source (same layout, same Redis class, identical description text 'A robust, performance-focused and full-featured Redis client for Node.js', and repository.url still points at git://github.com/luin/ioredis.git) but is published under the sibling name ioredis-orm. The package.json additionally declares a dependency on ioredis-typed: ^1.0.6, which is not the upstream ioredis project and is not documented in any README in the tarball. The shipped code itself contains no install hooks, no obfuscation, and no network/credential/exfil code paths — the supply-chain concern is the silently-pulled transitive ioredis-typed, which an installer who types npm install ioredis-orm (intending the legitimate ioredis) would acquire without notice. Routing to human review so a reviewer can assess the name-confusion risk and inspect ioredis-typed separately to determine whether the transitive carries a payload.
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
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for ioredis-orm (version 5.11.2).
If you installed it — respond
ioredis-orm 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-orm was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks ioredis-orm-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.