Which versions of @lui-ui/lui-vue are malicious?

The following npm versions of @lui-ui/lui-vue are flagged malicious: 1.0.13. Treat any of these as compromised.

How do I remediate @lui-ui/lui-vue if I installed it?

@lui-ui/lui-vue is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed @lui-ui/lui-vue — how do I know if it already compromised me?

If @lui-ui/lui-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 @lui-ui/lui-vue part of a known attack campaign?

Yes — @lui-ui/lui-vue is associated with the GHSA-mvx8-7fx3-6p38 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 @lui-ui/lui-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 @lui-ui/lui-vue (version 1.0.13). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @lui-ui/lui-vue across your stack and pipelines.

Malicious package

@lui-ui/lui-vuenpm

Malicious code in @lui-ui/lui-vue (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191245

Immediate action

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

npm uninstall @lui-ui/lui-vue

What this malware does

The package @lui-ui/lui-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.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

1 flagged

1.0.13

Indicators of compromise (SHA-256)

907ee7bca99a5287f756effe2de1d1eb821c961835c6fa011d88b79d908f52ab

339d88eca55085f7dbfd769a5800adf59a499c0e6e14500a6f456cf17ec249f0

59b88c15ab970fa80e2c420db246728871b310f27e35371206322bf8cea6abb1

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @lui-ui/lui-vue (version 1.0.13). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @lui-ui/lui-vue across your stack and pipelines.
If you installed it — respond
@lui-ui/lui-vue is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @lui-ui/lui-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 @lui-ui/lui-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. @lui-ui/lui-vue on npm has been identified as a malicious package (version 1.0.13 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-mvx8-7fx3-6p38

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @lui-ui/lui-vue-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring