Which versions of redis-type-xyz are malicious?

The following npm versions of redis-type-xyz are flagged malicious: 1.10.6. Treat any of these as compromised.

How do I remediate redis-type-xyz if I installed it?

redis-type-xyz 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 redis-type-xyz — how do I know if it already compromised me?

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.

Is redis-type-xyz part of a known attack campaign?

Yes — redis-type-xyz is associated with the IN-MAL-2026-012932 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 redis-type-xyz 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 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.

Malicious package

redis-type-xyznpm

redis-type-xyz is a confirmed malicious npm package (MAL-2026-11205) that steals credentials and exfiltrates sensitive data (malicious version 1.10.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in redis-type-xyz (npm)

MAL-2026-11205

Immediate action

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

npm uninstall redis-type-xyz

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.

Package is published as 'redis-type-xyz' but its README markets itself as 'redis-type-os', uses Redis branding/logo, and declares its repository as github:redis/redis-om-node — impersonating Redis's official redis-om library. The package's package.json declares main as 'dist/index.js' and types as './dist/index.d.ts', but no dist/ directory is present in the tarball, so require('redis-type-xyz') will throw MODULE_NOT_FOUND. The package is not a functional library. Its only on-install effect is dependency resolution: it declares a runtime dependency on 'ulid-xyz' (^2.12.2), a name-confusion variant of the legitimate 'ulid' package. Any consumer installing redis-type-xyz will transitively pull ulid-xyz from an unrelated publisher. The naming pattern (impersonation of a well-known library + a sibling 'xyz'-suffixed dep mirroring a popular package) is a name-confusion / namespace-lure shape, but the contents of ulid-xyz itself were not analyzed in this record and no installer-harm payload (exfiltration, install hooks, credential reads) is observed in the parent package's tarball. Routing to human review to assess intent of the ulid-xyz transitive and the impersonation pattern.

Malicious versions

1 flagged

1.10.6

Indicators of compromise (SHA-256)

c9c8e39757a709b00e180a43959cd14e8cd36922e2f3b9a19f75046bd79e767c

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

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

Campaign

IN-MAL-2026-012932

References

Credits

Amazon Inspector · finder
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 credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database