redis-type-xyznpm
redis-type-xyz is a confirmed malicious npm package (MAL-2026-11205) that opens a backdoor for remote access (malicious version 1.10.6). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in redis-type-xyz (npm)
What this malware does
The redis-type-xyz package is an empty impersonation of Redis OM. It copies the redis-om-node repository, homepage, author, documentation, and declared dist/index.js entry point, but the published archive does not contain the declared dist directory or any usable implementation. Its dependency list replaces the legitimate ulid package used by Redis OM with ulid-xyz@^2.12.2.
Installing redis-type-xyz therefore installs the known-malicious ulid-xyz dependency. The ulid-xyz postinstall hook launches a detached background agent that decodes a WebSocket and HTTP C2 endpoint at 95.216.232.162:8010. The agent supports system information collection, drive and directory enumeration, removal, and deploy_binary tasks. deploy_binary writes attacker-supplied Base64 content to disk, registers persistence on Windows, macOS, or Linux, and launches the replacement agent. The malicious ulid-xyz dependency is independently tracked as MAL-2026-6672. redis-type-xyz is a separate delivery package that intentionally substitutes the known-malicious dependency into an otherwise copied Redis OM manifest.
Malicious versions
Detection & response playbook
Backdoor / remote accessFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for redis-type-xyz (version 1.10.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging redis-type-xyz across your stack and pipelines.
If you installed it — respond
redis-type-xyz establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If redis-type-xyz 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 redis-type-xyz 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
References
Credits
- YoSheep · finder
Detect & block this
O3 blocks redis-type-xyz-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.