Which versions of example-vue2-micro are malicious?

The following npm versions of example-vue2-micro are flagged malicious: 999.0.104. Treat any of these as compromised.

How do I remediate example-vue2-micro if I installed it?

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

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

Yes — example-vue2-micro is associated with the GHSA-9rqv-9897-8v59, RLMA-2026-01301 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 example-vue2-micro 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 example-vue2-micro (version 999.0.104). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging example-vue2-micro across your stack and pipelines.

Malicious package

example-vue2-micronpm

Malicious code in example-vue2-micro (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-192590

Immediate action

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

npm uninstall example-vue2-micro

What this malware does

The package example-vue2-micro 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

999.0.104

Indicators of compromise (SHA-256)

9fc746164e0f367cded45fee0697db79ea9afdde75a0ab3a19d6448bf31fae40

1cda06e9583d6e3b61afb6f1134f4d867559022d5844de0fbb5781312b8d5abc

a85d5bca7965c7db1338ef8baa4858c6924e32ff4af66c94b9654a17a198f086

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

Campaign

GHSA-9rqv-9897-8v59RLMA-2026-01301

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks example-vue2-micro-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