Which versions of csv-parsing-xyz are malicious?

The following npm versions of csv-parsing-xyz are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate csv-parsing-xyz if I installed it?

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

If csv-parsing-xyz was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is csv-parsing-xyz part of a known attack campaign?

Yes — csv-parsing-xyz is associated with the GHSA-mrvm-whxc-m2c3, RLMA-2025-05337, RLUA-2025-05711 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 csv-parsing-xyz across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for csv-parsing-xyz (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging csv-parsing-xyz across your stack and pipelines.

Malicious package

csv-parsing-xyznpm

csv-parsing-xyz is a confirmed malicious npm package (MAL-2025-48414) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in csv-parsing-xyz (npm)

MAL-2025-48414

Immediate action

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

npm uninstall csv-parsing-xyz

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

1 flagged

1.0.0

Indicators of compromise (SHA-256)

363b0535fad3e1200b4ecbbcaf6864c57f005f66af100032426235146347282e

fc456ba8453f86a912c5df230f1966dd2496d44fc3379eea1caa7c63ebfd710f

f6f47659a86853d0ed774bdf1d5ee4ca9377d467cd6925e7190852ae334b706d

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for csv-parsing-xyz (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging csv-parsing-xyz across your stack and pipelines.
If you installed it — respond
Remove csv-parsing-xyz 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 csv-parsing-xyz was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks csv-parsing-xyz before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

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

Campaign

GHSA-mrvm-whxc-m2c3RLMA-2025-05337RLUA-2025-05711

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks csv-parsing-xyz-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