Which versions of @rblxts/services are malicious?

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

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

@rblxts/services is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed @rblxts/services — how do I know if it already compromised me?

If @rblxts/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.

Is @rblxts/services part of a known attack campaign?

Yes — @rblxts/services is associated with the IN-MAL-2026-017255, IN-MAL-2026-017260 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 @rblxts/services across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @rblxts/services (2 malicious versions).

Malicious package

@rblxts/servicesnpm

Advisory published Aug 10, 2026Updated Aug 10, 2026

@rblxts/services is a confirmed malicious npm package (MAL-2026-13691) that steals credentials and exfiltrates sensitive data (malicious versions 1.6.0, 1.6.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @rblxts/services (npm)

MAL-2026-13691

Immediate action

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

npm uninstall @rblxts/services

What this malware does

@rblxts/services is a typosquat of @rbxts/services. Its scripts/postinstall.js is heavily obfuscated: module names ('fs','https','child_process'), environment variable names, filenames, and the download URL are stored as \x hex escapes or base64 to hide them from string scanners. On Windows, the postinstall decodes a base64 URL to https://files.catbox.moe/vpfwzj.zip, downloads the archive, uses PowerShell Expand-Archive to unpack it into a randomly-named directory under %LOCALAPPDATA%\Microsoft, and then spawns a bundled pythonw.exe against exec_.py with detached:true, windowsHide:true and stdio ignored, unref'd from the installer process. The delivery host (files.catbox.moe) is an anonymous file locker, the URL is not pinned by hash, the staging path is hidden under a Microsoft-lookalike directory, and the entire chain fires automatically on npm install.

Malicious versions

2 flagged

1.6.01.6.2

Indicators of compromise (SHA-256)

493084027acef5e5ee72f7f86aee9c3dd6d901c10ddb013645b5594ca0fbb672

f1f58d29f68e2d431a9a6e55f49b0441dabb7601accfecb3c1801aabd30e29d0

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for @rblxts/services (2 malicious versions).
If you installed it — respond
@rblxts/services is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @rblxts/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

No. @rblxts/services on npm has been identified as a malicious package (versions 1.6.0, 1.6.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-017255IN-MAL-2026-017260

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @rblxts/services-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database