Which versions of quicksolving are malicious?

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

How do I remediate quicksolving if I installed it?

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

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

Yes — quicksolving 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 quicksolving 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 quicksolving (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 quicksolving across your stack and pipelines.

Malicious package

quicksolvingPyPI

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

MAL-2026-3044

Immediate action

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

pip uninstall quicksolving

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)

334524bfbf6438acc5016e76054740cdb532bdd9921695cbcc1852c568226708

6ce7101503fd7e3f5a973cf98552f2403086e47a50dd13fb7170b51497354160

f4e30d78acb51b567e6bdb96eb7f5acb1da10b32c670c377cb9495610579c028

6348b0a1cc0eb321b58ad555f936c8c2adcc3430ee33c086ec8081cbfb2c7e0c

2114f54cd5b18972a7d6239eb1923833f3974a3a43bf5bae5b4f7e73244db813

d96403c16533ae4895571b4b41de94e422ebc13bb185ae1a229c48c264e8b61c

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 quicksolving (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 quicksolving across your stack and pipelines.
If you installed it — respond
quicksolving 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 quicksolving 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 quicksolving 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. quicksolving 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 quicksolving-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