ioredis-os

Details

---
_-= Per source details. Do not edit below this line.=-_

## Source: amazon-inspector (387bee0d123eeed248b8be6281784b88d2a3385943a3f696541c1ce48b1c817a)
`ioredis-os` appends `-os` to the widely-used `ioredis` package name and ships what appears to be a verbatim fork of ioredis (same author, same upstream repository URL `git://github.com/luin/ioredis.git`, identical API surface). It also declares a dependency on `redis-type-os`, another `-os`-suffixed name that mirrors `redis-type`. No install lifecycle scripts are declared and no credential theft, exfiltration, dropper, or silent-relay behavior is present in the reachable code from `built/index.js` — the current code looks clean. The concern is the naming pattern: a developer who mistypes or otherwise reaches `ioredis-os` instead of `ioredis` ends up running a fork that the upstream maintainer does not control, and the chained `-os` dependency expands that surface. Routing to human review so a maintainer can assess whether the fork is legitimate (intended derivative) or a name-confusion squat that should be removed.

## Source: ghsa-malware (e2f2ca304bd9e06abf9eb5b702b23180abd718e67dee78dc27fc3255c3f18bec)
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.

Compromised versions (1)

• 5.10.2

Any computer that installed or ran a compromised version should be considered fully compromised. Rotate every secret on that machine from a clean environment.