Which versions of plugin-vue are malicious?

The following npm versions of plugin-vue are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate plugin-vue if I installed it?

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

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

Yes — plugin-vue is associated with the GHSA-hxxj-55p6-h93r, RLMA-2026-01499 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 plugin-vue 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 plugin-vue (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging plugin-vue across your stack and pipelines.

Malicious package

plugin-vuenpm

Malicious code in plugin-vue (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-425

Immediate action

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

npm uninstall plugin-vue

What this malware does

The package plugin-vue 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

1 flagged

1.0.1

Indicators of compromise (SHA-256)

5dd13d282d1e3afa8890341ff538701132443043511faaac6d79e562de074cb3

03d02d8d83b614a55ba66663cbaa93bfc062bb8de63f438fcd60bea960610a5f

40c8bd739979793279f8531233605bb0047943a576403281a2cab84aa364d0a6

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

Campaign

GHSA-hxxj-55p6-h93rRLMA-2026-01499

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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