Which versions of @rbx-ts/services are malicious?

The following npm versions of @rbx-ts/services are flagged malicious: 1.6.0, 1.6.1, 1.6.2. Treat any of these as compromised.

How do I remediate @rbx-ts/services if I installed it?

@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.

I already installed @rbx-ts/services — how do I know if it already compromised me?

If @rbx-ts/services 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 @rbx-ts/services part of a known attack campaign?

Yes — @rbx-ts/services is associated with the IN-MAL-2026-017169, IN-MAL-2026-017253, IN-MAL-2026-017252 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 @rbx-ts/services 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 @rbx-ts/services (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @rbx-ts/services across your stack and pipelines.

Malicious package

@rbx-ts/servicesnpm

@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)

MAL-2026-13630

Immediate action

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

npm uninstall @rbx-ts/services

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

3 flagged

1.6.01.6.11.6.2

Indicators of compromise (SHA-256)

22a1774c78b52b3d507d305227a1a258795a4e68d52b8366e0010c5d0bb80126

9476bbe7c2ce12348142e93deffe53c9d4d6dfef3400030af81cff902bac5935

f3883a4eaf1f35ec3de7789b864b2c402769c31d13b0bc150e1e7d47e22c8eb9

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 @rbx-ts/services (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @rbx-ts/services across your stack and pipelines.
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 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 @rbx-ts/services 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. @rbx-ts/services on npm has been identified as a malicious package (versions 1.6.0, 1.6.1, 1.6.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-017169IN-MAL-2026-017253IN-MAL-2026-017252

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database