Which versions of rojo-rbx are malicious?

The following npm versions of rojo-rbx are flagged malicious: 1.4.3. Treat any of these as compromised.

How do I remediate rojo-rbx if I installed it?

rojo-rbx is a typosquat — you almost certainly intended a legitimately-named package. Remove rojo-rbx, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed rojo-rbx — how do I know if it already compromised me?

If rojo-rbx 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 rojo-rbx part of a known attack campaign?

Yes — rojo-rbx is associated with the IN-MAL-2026-019731 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 rojo-rbx 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 rojo-rbx (version 1.4.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging rojo-rbx across your stack and pipelines.

Malicious package

rojo-rbxnpm

rojo-rbx is a confirmed malicious npm package (MAL-2026-16059) that typosquats a legitimate package to trick installs (malicious version 1.4.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in rojo-rbx (npm)

MAL-2026-16059

Immediate action

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

npm uninstall rojo-rbx

What this malware does

The package impersonates the legitimate Rojo Roblox tooling project. Its npm install lifecycle runs scripts/install.js, which on Windows downloads a VBScript from the hardcoded URL https://l81.me/updater.vbs, writes it to %APPDATA%\Rojo\rojo-sync.vbs, and executes it hidden via wscript.exe //B. The script then adds an HKCU\Software\Microsoft\Windows\CurrentVersion\Run entry named RojoClientSync that re-launches the dropped VBS on every user login, giving the fetched payload boot persistence independent of the package. The remote URL, wscript.exe, //B flag, target directory, file name, registry path, and value name are all reconstructed at runtime from String.fromCharCode numeric arrays via a _d() helper to evade static review. The shipped bin only prints --version/--help and provides no functional Rojo CLI; the manifest points at github.com/Unreal-Works/rojo-npm rather than the real rojo-rbx/rojo project. The dropper is the package's only real behavior.

Malicious versions

1 flagged

1.4.3

Indicators of compromise (SHA-256)

8bf25c0dd3a1b933c3ee2fe887301590c3b92e383a1e6c380fcdb9544578720b

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for rojo-rbx (version 1.4.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging rojo-rbx across your stack and pipelines.
If you installed it — respond
rojo-rbx is a typosquat — you almost certainly intended a legitimately-named package. Remove rojo-rbx, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If rojo-rbx 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 rojo-rbx 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. rojo-rbx on npm has been identified as a malicious package (version 1.4.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-019731

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks rojo-rbx-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