MalwarePublished 16 Jun 2026Updated 9 Jul 2026

redis-type-os (npm) · Malicious Code

Affects redis-type-osSource GCVE Database

Malicious package : remove redis-type-os and rotate any secrets on hosts that installed it.

Data as of 11 Jul 2026, 09:43 UTC

Classification

Malicious package

Published to npm · OSV MAL-2026-5882

What to do

Remove redis-type-os from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.

Affected software

Product	Affected	Fixed in
npmredis-type-os	Affected 1.0.3 – 1.0.10 4 affected builds	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (8f9fefcfb296b7a9b0c08dc47f628f1987d349d5b57cc9b3c5cb2ce7e331f7e4) Package is published as `redis-type-os` but all in-package references (README, docs/, CHANGELOG, repository field, author email) point to `redis-om` / `redis-om-node` by Guy Royse. `dist/index.js` is the upstream redis-om bundle verbatim. The only meaningful divergence from upstream is an added runtime dependency `hex-type@^3.0.2` declared in `package.json`, which is not imported anywhere in the shipped code. The package itself contains no exfiltration, dropper, install hook, or credential-handling code; the carrier ships legitimate redis-om functionality. The supply-chain concern is two-fold: (1) the package name (`redis-type-os` vs `redis-om`) plus impersonated author identity creates confusion for developers who mistype the real package, and (2) installing it silently pulls `hex-type` into the dependency closure for reasons unrelated to the advertised functionality. Whether `hex-type` itself is benign or malicious must be evaluated separately. Routed for human review because name-similarity and author-impersonation are subjective judgments and the carrier itself executes no harmful code at install or import time. ## Source: ghsa-malware (99c007b1300db882ef2517bb7c64d7ecc069ad07d404c8b56c66b846b75bab49) 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.

Impact

Installing redis-type-os may result in full compromise of the affected system, as indicated by security advisories. All secrets and keys on the system should be considered exposed and require immediate rotation. Removal of the package alone may not eliminate all malicious artifacts due to potential persistent compromise. The package's impersonation and added dependency increase the risk of supply chain attacks.

Defensive guidance

Immediate removal of the package is recommended. All secrets and keys stored on the affected system should be rotated from a separate, trusted environment. Monitor for any signs of persistent compromise beyond the package installation.

Summary

redis-type-os is a malicious npm package that impersonates the legitimate redis-om package by copying its code and author metadata but adds an unexplained dependency on hex-type. The package does not contain direct malicious payloads such as exfiltration or install hooks but creates supply chain risk through author impersonation and dependency confusion. Security advisories indicate that installing redis-type-os may lead to full system compromise, necessitating secret rotation and removal of the package.

References

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 9 Jul 2026, 09:53 UTC

Technical details

References

Community reviews