Which versions of oracle-redis are malicious?

The following npm versions of oracle-redis are flagged malicious: 5.11.3. Treat any of these as compromised.

How do I remediate oracle-redis if I installed it?

Remove oracle-redis from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed oracle-redis — how do I know if it already compromised me?

If oracle-redis 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 oracle-redis part of a known attack campaign?

Yes — oracle-redis is associated with the IN-MAL-2026-020298 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 oracle-redis 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 oracle-redis (version 5.11.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging oracle-redis across your stack and pipelines.

Malicious package

oracle-redisnpm

oracle-redis is a confirmed malicious npm package (MAL-2026-16390) that executes malicious code on install (malicious version 5.11.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in oracle-redis (npm)

MAL-2026-16390

Immediate action

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

npm uninstall oracle-redis

What this malware does

The package publishes as oracle-redis but ships a verbatim copy of the ioredis README, source tree, and repository URL (git://github.com/luin/ioredis.git), presenting itself as ioredis under a different name. The package.json declares two additional runtime dependencies that are not part of ioredis's real dependency set and are never imported anywhere in the shipped built/ source: redis-type-intel ^1.10.5 and pino-ulid ^2.12.2. Because they are ordinary dependencies with caret ranges, npm install oracle-redis resolves and installs those two packages (and their transitive graph) into the installer's node_modules, executing whatever lifecycle scripts they declare, even though nothing in the ioredis code being wrapped ever loads them. The combination of a name-squat lure over a popular library plus unused, caret-pinned extra dependencies is a dependency-delivery shape: the harm, if any, arrives through the transitive install of the extra names rather than through this tarball's own code.

Malicious versions

1 flagged

5.11.3

Indicators of compromise (SHA-256)

c800d0651330b1c1cd5d9c5cb2b6966eecefb2d2c28949d0670f485d820db3a6

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for oracle-redis (version 5.11.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging oracle-redis across your stack and pipelines.
If you installed it — respond
Remove oracle-redis from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If oracle-redis 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 oracle-redis 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. oracle-redis on npm has been identified as a malicious package (version 5.11.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020298

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks oracle-redis-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database