Which versions of vue_frontend_rpc are malicious?

Every published version of vue_frontend_rpc on npm is considered malicious. Remove the package entirely.

How do I remediate vue_frontend_rpc if I installed it?

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

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

Yes — vue_frontend_rpc is associated with the GHSA-x89m-w75w-f74w 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 vue_frontend_rpc 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 vue_frontend_rpc (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging vue_frontend_rpc across your stack and pipelines.

Malicious package

vue_frontend_rpcnpm

Malicious code in vue_frontend_rpc (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-319

Immediate action

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

npm uninstall vue_frontend_rpc

What this malware does

The package vue_frontend_rpc 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.

Malicious versions

all versions

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

Indicators of compromise (SHA-256)

37b3b39f0c20a8dd65bccdba671ecc5761e03146f454226847e982c424b8c25b

30e31020ae5911a45b568d33238a4785bb2149dc1a8b474ac220aacb60546551

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 vue_frontend_rpc (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging vue_frontend_rpc across your stack and pipelines.
If you installed it — respond
Remove vue_frontend_rpc 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 vue_frontend_rpc 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 vue_frontend_rpc 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. vue_frontend_rpc 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-x89m-w75w-f74w

References

github.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks vue_frontend_rpc-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