Which versions of @rbxst/services are malicious?

The following npm versions of @rbxst/services are flagged malicious: 1.0.756. Treat any of these as compromised.

How do I remediate @rbxst/services if I installed it?

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

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

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

Malicious package

@rbxst/servicesnpm

@rbxst/services is a confirmed malicious npm package (MAL-2026-13521) that executes malicious code on install (malicious version 1.0.756). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @rbxst/services (npm)

MAL-2026-13521

Immediate action

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

npm uninstall @rbxst/services

What this malware does

scripts/postinstall.js runs at npm install time. On Windows it downloads a ZIP archive from https://files.catbox.moe/rp8idk.zip (anonymous file-hosting service, mutable content), uses PowerShell Expand-Archive to unpack it to a randomized temp directory, then spawns a bundled pythonw.exe against exec_.py with detached:true, stdio:'ignore', windowsHide:true, and child.unref(), so the fetched payload runs hidden and outlives the npm process. The script exits silently on non-Windows platforms. The package advertises roblox-ts service type utilities and has no legitimate need to fetch and execute a Python interpreter from an anonymous file host. This matches the alternate-runtime dropper pattern from known-bad infrastructure: an opaque remote payload executes on the installer's machine with the installer's privileges.

Malicious versions

1 flagged

1.0.756

Indicators of compromise (SHA-256)

f8e349df2092cb3672698c00cefa5268881f21a60d1f71394c9e223b40d086d2

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

Campaign

IN-MAL-2026-016991

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @rbxst/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