Which versions of vite-plugin-parseflow are malicious?

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

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

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

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

Yes — vite-plugin-parseflow is associated with the GHSA-rmxp-8xjf-4jjq, RLMA-2025-05992, RLUA-2025-06530 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-parseflow 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-parseflow (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-parseflow across your stack and pipelines.

Malicious package

vite-plugin-parseflownpm

vite-plugin-parseflow is a confirmed malicious npm package (MAL-2025-48426) 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-parseflow (npm)

MAL-2025-48426

Immediate action

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

npm uninstall vite-plugin-parseflow

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)

6264d2fd8e60e842a2b4b3e0d5b8da287d27e021ff47460da70171fb82adf3b0

3eb16f1fc54ea0c4aa221677675b4cb0757656207def3b6c29226d35a49419df

a0a0083d8051c1b90b23e99eb20d0c78b2cad9edce20ca67bdf7ed3484cd0c3b

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-parseflow (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-parseflow across your stack and pipelines.
If you installed it — respond
Remove vite-plugin-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 vite-plugin-parseflow 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-parseflow 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-parseflow 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-rmxp-8xjf-4jjqRLMA-2025-05992RLUA-2025-06530

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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