Which versions of redis-request-parser are malicious?

The following npm versions of redis-request-parser are flagged malicious: 1.2.6. Treat any of these as compromised.

How do I remediate redis-request-parser if I installed it?

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

If redis-request-parser was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is redis-request-parser part of a known attack campaign?

Yes — redis-request-parser is associated with the GHSA-wffw-vj4r-vqc2 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-request-parser across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for redis-request-parser (version 1.2.6).

Malicious package

redis-request-parsernpm

Advisory published Jan 6, 2026Updated Jan 8, 2026

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

Malicious code in redis-request-parser (npm)

MAL-2026-71

Immediate action

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

npm uninstall redis-request-parser

What this malware does

The package redis-request-parser was found to contain malicious code.

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.

The OpenSSF Package Analysis project identified 'redis-request-parser' @ 1.2.6 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

1.2.6

Indicators of compromise (SHA-256)

e6cc5a25680323a180b3c0873ab19295e6418355a9660e98c89bbdd5a0516802

088cee260bffba27089bfe90d6221d9f72aa79c3ae9dc65edc490ec0f528d172

c98c3985913e00b5e728a27ab47c68589ba0e478f576fa6ed9aed1c42d229972

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for redis-request-parser (version 1.2.6).
If you installed it — respond
Remove redis-request-parser 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 redis-request-parser was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

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

Campaign

GHSA-wffw-vj4r-vqc2

References

github.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks redis-request-parser-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