Which versions of vubiquity-website are malicious?

The following npm versions of vubiquity-website are flagged malicious: 3.9.10. Treat any of these as compromised.

How do I remediate vubiquity-website if I installed it?

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

If vubiquity-website was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is vubiquity-website part of a known attack campaign?

Yes — vubiquity-website is associated with the RLMA-2026-05357, RLUA-2026-06543 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 vubiquity-website across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for vubiquity-website (version 3.9.10).

Malicious package

vubiquity-websitenpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

vubiquity-website is a confirmed malicious npm package (MAL-2026-7433) that executes malicious code on install (malicious version 3.9.10). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in vubiquity-website (npm)

MAL-2026-7433

Immediate action

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

npm uninstall vubiquity-website

Malicious versions

1 flagged

3.9.10

Indicators of compromise (SHA-256)

ddf5dc8d03fb53963c705e851a962fe50bb9d4a0d5b55a67217e54c8406c71d4

7dd1879c170d1e0ffc61e922b042f1439d02f9e0960b201a5a35c288d3b92b8b

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for vubiquity-website (version 3.9.10).
If you installed it — respond
Remove vubiquity-website 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 vubiquity-website was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. vubiquity-website on npm has been identified as a malicious package (version 3.9.10 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-05357RLUA-2026-06543

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks vubiquity-website-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