@rbx-ts/servicesnpm
Advisory published Updated
@rbx-ts/services is a confirmed malicious npm package (MAL-2026-13630) that typosquats a legitimate package to trick installs (malicious versions 1.6.0, 1.6.1, 1.6.2). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @rbx-ts/services (npm)
What this malware does
This package impersonates the @rbxts/services Roblox typings library and re-exports its public API in index.js as cover. Its postinstall script (scripts/postinstall.js) is gated to win32 and uses \x hex escapes to hide the strings 'child_process', 'spawn', 'powershell', and related identifiers. It spawns a hidden PowerShell process with -ExecutionPolicy Bypass, passing a base64-encoded body that decodes to an AMSI bypass (patched via reflection with strings split across variables to evade signature scanning), downloads a binary from https://files.catbox.moe/a3loxy.bin, allocates RWX memory via VirtualAlloc with protection 0x40, copies the downloaded bytes into it, and executes them via CreateThread. Installing this package on Windows results in arbitrary attacker shellcode executing in the installer's process on npm install.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
TyposquatFind it
Search your lockfiles and build artifacts for @rbx-ts/services (3 malicious versions).
If you installed it — respond
@rbx-ts/services is a typosquat — you almost certainly intended a legitimately-named package. Remove @rbx-ts/services, 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 @rbx-ts/services 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks @rbx-ts/services-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.