Which versions of @postman/csv-parse are malicious?

The following npm versions of @postman/csv-parse are flagged malicious: 4.0.3, 4.0.4, 4.0.5. Treat any of these as compromised.

How do I remediate @postman/csv-parse if I installed it?

@postman/csv-parse is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed @postman/csv-parse — how do I know if it already compromised me?

If @postman/csv-parse 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 @postman/csv-parse part of a known attack campaign?

Yes — @postman/csv-parse is associated with the GHSA-j942-2f3x-w9mc 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 @postman/csv-parse across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @postman/csv-parse (3 malicious versions).

Part of a larger attack: @postman published 17 malicious packages. See the full campaign →

Malicious package

@postman/csv-parsenpm

Advisory published Nov 24, 2025Updated Nov 26, 2025

@postman/csv-parse is a confirmed malicious npm package (MAL-2025-190646) that steals credentials and exfiltrates sensitive data (malicious versions 4.0.3, 4.0.4, 4.0.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @postman/csv-parse (npm)

MAL-2025-190646

Immediate action

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

npm uninstall @postman/csv-parse

What this malware does

The package @postman/csv-parse 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.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

3 flagged

4.0.34.0.44.0.5

Indicators of compromise (SHA-256)

d202a54763fdb04cca410c9b50d1a6972563df3bc754d1c04475cb0989d0e073

6072df393f967e34b9e50f3c9843f4716a7e65e30aff5648c7f003cb37c38e01

efe55c69c5e92f438e96dd72658ed2d9438342776626bfee388876f1fa803717

dc41c207307bafc4887adf871b4165ff7a612098c64a269f7553425c44c0d19d

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for @postman/csv-parse (3 malicious versions).
If you installed it — respond
@postman/csv-parse is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @postman/csv-parse 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. @postman/csv-parse on npm has been identified as a malicious package (versions 4.0.3, 4.0.4, 4.0.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-j942-2f3x-w9mc

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @postman/csv-parse-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database