Which versions of cookie-parser-legacy are malicious?

Every published version of cookie-parser-legacy on npm is considered malicious. Remove the package entirely.

How do I remediate cookie-parser-legacy if I installed it?

Remove cookie-parser-legacy 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 network activity or persistence. Use O3 Security's dependency scanner to confirm the package and its artifacts are fully purged across your stack.

Is cookie-parser-legacy part of a known attack campaign?

Yes — cookie-parser-legacy is associated with the GHSA-xv3p-wcmf-6hp8 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

Can O3 Security detect cookie-parser-legacy in my codebase?

Yes. O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, blocking cookie-parser-legacy and packages like it before any post-install script runs.

Malicious package

cookie-parser-legacynpm

Malicious code in cookie-parser-legacy (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-5346

Immediate action

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

npm uninstall cookie-parser-legacy

What this malware does

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.

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

1b0e373057d636dbc4939fdb3e1f8cda1276c8bb88ae02f5ed156244e12fdb91

Frequently asked questions

No. cookie-parser-legacy on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-xv3p-wcmf-6hp8

References

github.com

Scan your dependencies

O3 Security blocks malicious packages like this at install time and in CI.

Supply-chain protection