Which versions of lui-vue-test are malicious?

The following npm versions of lui-vue-test are flagged malicious: 0.70.9. Treat any of these as compromised.

How do I remediate lui-vue-test if I installed it?

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

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

Yes — lui-vue-test is associated with the GHSA-qj5r-2cxx-2pj6 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-vue-test 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-vue-test (version 0.70.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging lui-vue-test across your stack and pipelines.

Malicious package

lui-vue-testnpm

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

MAL-2025-191125

Immediate action

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

npm uninstall lui-vue-test

What this malware does

The package lui-vue-test 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

0.70.9

Indicators of compromise (SHA-256)

390e4d5770dff6841abe0c2eb89f94237238ea21ec3811361c614593c28ee002

3fa5a4755196603a05c468b0696b82f3a4725b0f133aeb9f6b1b3a297b4f9a30

c1ec012cfb1edfb9761b430b0782b52888c004d3b836117ecf2e28bd16e62d5b

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

Campaign

GHSA-qj5r-2cxx-2pj6

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks lui-vue-test-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