Which versions of rtxbbtyols are malicious?

The following npm versions of rtxbbtyols are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate rtxbbtyols if I installed it?

rtxbbtyols 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 rtxbbtyols — how do I know if it already compromised me?

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

Yes — rtxbbtyols is associated with the GHSA-ggfg-9547-fcfq, RLMA-2026-01542, RLUA-2026-01812 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 rtxbbtyols 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 rtxbbtyols (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging rtxbbtyols across your stack and pipelines.

Malicious package

rtxbbtyolsnpm

Malicious code in rtxbbtyols (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-1027

Immediate action

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

npm uninstall rtxbbtyols

What this malware does

Package collects and exfiltrates sensitive info to oastify.com via HTTP in both index.js and setup.py with silent error handling.

The package rtxbbtyols was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

7a545131c0d6f2f8be5e52e2d51ba1ca4bc79095868f4b3c8169744110c68ecd

a2d816967784c850ba8bdfb19a7a2fffe29f35a5850efbfc3cc3e342d8366785

070d5c179987d5bfdf22a35ed392e342cafde4af3d0931a3ff8289956ea8000e

39a22b851212146553a510c525d33928d10a9e57e21b65247e61934e08f3c8c3

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for rtxbbtyols (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging rtxbbtyols across your stack and pipelines.
If you installed it — respond
rtxbbtyols 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 rtxbbtyols 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 rtxbbtyols 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. rtxbbtyols on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-ggfg-9547-fcfqRLMA-2026-01542RLUA-2026-01812

References

Credits

Amazon Inspector · finder
ReversingLabs · finder
SafeDep · finder

Detect & block this

O3 blocks rtxbbtyols-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