Which versions of cookie-parseflow are malicious?

The following npm versions of cookie-parseflow are flagged malicious: 1.5.8. Treat any of these as compromised.

How do I remediate cookie-parseflow if I installed it?

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

If cookie-parseflow 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 cookie-parseflow part of a known attack campaign?

Yes — cookie-parseflow is associated with the RLMA-2026-05034, RLUA-2026-06167 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 cookie-parseflow across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for cookie-parseflow (version 1.5.8).

Malicious package

cookie-parseflownpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

cookie-parseflow is a confirmed malicious npm package (MAL-2026-7247) that executes malicious code on install (malicious version 1.5.8). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in cookie-parseflow (npm)

MAL-2026-7247

Immediate action

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

npm uninstall cookie-parseflow

Malicious versions

1 flagged

1.5.8

Indicators of compromise (SHA-256)

26116bf555ccc727891ab5723ca93fb3cdfcd4e134150b8ea319376da394f82f

5b2a8e21ab968f6bd9d46e12f1b47fda73f47f166fddab9a43b0c45d6459a08f

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for cookie-parseflow (version 1.5.8).
If you installed it — respond
Remove cookie-parseflow 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 cookie-parseflow 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. cookie-parseflow on npm has been identified as a malicious package (version 1.5.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-05034RLUA-2026-06167

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks cookie-parseflow-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