Which versions of vite-plugin-parsify are malicious?

The following npm versions of vite-plugin-parsify are flagged malicious: 2.0.1. Treat any of these as compromised.

How do I remediate vite-plugin-parsify if I installed it?

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

If vite-plugin-parsify 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 vite-plugin-parsify part of a known attack campaign?

Yes — vite-plugin-parsify is associated with the GHSA-q53f-qp4v-c97p, RLMA-2025-05993, RLUA-2025-06531 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 vite-plugin-parsify 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 vite-plugin-parsify (version 2.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging vite-plugin-parsify across your stack and pipelines.

Malicious package

vite-plugin-parsifynpm

vite-plugin-parsify is a confirmed malicious npm package (MAL-2025-48784) that executes malicious code on install (malicious version 2.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in vite-plugin-parsify (npm)

MAL-2025-48784

Immediate action

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

npm uninstall vite-plugin-parsify

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

2.0.1

Indicators of compromise (SHA-256)

031b7573beae98422d50771f010df5ea83910b304700e644b2e5b8cb6111aa59

83e01702d3ada7e7c646121a244c5473e9994e8419d761e55f9e74033db95a04

1d06254d448caf5a636780251c3d81e02ce42ccd34a0fcb8c83c76df75f1d789

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 vite-plugin-parsify (version 2.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging vite-plugin-parsify across your stack and pipelines.
If you installed it — respond
Remove vite-plugin-parsify 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 vite-plugin-parsify 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 vite-plugin-parsify 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. vite-plugin-parsify on npm has been identified as a malicious package (version 2.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-q53f-qp4v-c97pRLMA-2025-05993RLUA-2025-06531

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks vite-plugin-parsify-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