Which versions of @expue/vue-renderer are malicious?

The following npm versions of @expue/vue-renderer are flagged malicious: 0.0.3-alpha.0. Treat any of these as compromised.

How do I remediate @expue/vue-renderer if I installed it?

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

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

Yes — @expue/vue-renderer is associated with the RLMA-2024-00068, RLUA-2024-05918 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 @expue/vue-renderer 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 @expue/vue-renderer (version 0.0.3-alpha.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @expue/vue-renderer across your stack and pipelines.

Part of a larger attack: @expue published 11 malicious packages. See the full campaign →

Malicious package

@expue/vue-renderernpm

@expue/vue-renderer is a confirmed malicious npm package (MAL-2024-3839) that executes malicious code on install (malicious version 0.0.3-alpha.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @expue/vue-renderer (npm)

MAL-2024-3839

Immediate action

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

npm uninstall @expue/vue-renderer

Malicious versions

1 flagged

0.0.3-alpha.0

Indicators of compromise (SHA-256)

26c0ecd2726fddafdd922452b0d71a88916ba7df7322cee8f5717e5ebbd6b343

788869ba0ce8008be5e9f2ec4d655e691973caadc188bc25affc4e202d15af06

898a99ce1ec3b5e065e068000ef493edf1e5892e5820177ed74b38f2021610a5

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

Campaign

RLMA-2024-00068RLUA-2024-05918

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks @expue/vue-renderer-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

Explore

All malware advisories How O3 detects malware Vulnerability database