Which versions of quicktestybesty are malicious?

The following PyPI versions of quicktestybesty are flagged malicious: 2.3.0. Treat any of these as compromised.

How do I remediate quicktestybesty if I installed it?

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

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

Yes — quicktestybesty is associated with the 2026-03-roboat-addition 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 quicktestybesty 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 quicktestybesty (version 2.3.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging quicktestybesty across your stack and pipelines.

Malicious package

quicktestybestyPyPI

Malicious code in quicktestybesty (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-3045

Immediate action

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

pip uninstall quicktestybesty

What this malware does

During installation package downloads and runs a malicious executable. Likely continuation of 2026-03-rowrap.

The campaign is built over a malicious Roblox API wrapper. The roboat[.]pro (later robase[.]app) domain advertises a wrapper that is either directly malicious (as roboat collected in the campaign 2026-03-rowrap) or uses a malicious dependencies (like roboat-utils). New versions are published simultaneously with malicious dependencies and quickly removed. Another advertisement channel is https://github.com/Addi9000/roboat referencing two active contributors: https://github.com/Addi9000 and https://github.com/RoCruise

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2026-03-roboat-addition

Reasons (based on the campaign):

The package overrides the install command in setup.py to execute malicious code during installation.
Downloads and executes a remote executable.
The malicious code is intentionally included in a dependency of the package
malware
clones-real-package

Malicious versions

1 flagged

2.3.0

Indicators of compromise (SHA-256)

459aa54bf8ac82101b14d4f85d01dde304aa638276b69a76254ff080ea52d5af

1a0500f34c132b6d1777e6b0d89730ceb7b4df513a7c68f69f8e6f8b85e005d7

6cd40ab92a98305b578eac621f835abb3ac3f240c625405e50565856fc800db1

bcb4668da25fb887c8d47f9c8841f127db9ce61a8630a3e1ecf0ae8e99378252

53158d2f31b64abe9d8c57c93f2034246d969bccbfcd7ae53c214c95071e0d5f

235f27ee5c130c9bf63b4a606d064e97c6b8a4da75b007e4210a83d809ae0cad

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

Campaign

2026-03-roboat-addition

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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