Which versions of sqiul83 are malicious?

The following PyPI versions of sqiul83 are flagged malicious: 1.0. Treat any of these as compromised.

How do I remediate sqiul83 if I installed it?

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

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

Yes — sqiul83 is associated with the RLMA-2025-03695, 2025-06-sqiul83, RLUA-2026-00778 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 sqiul83 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 sqiul83 (version 1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging sqiul83 across your stack and pipelines.

Malicious package

sqiul83PyPI

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

MAL-2025-6596

Immediate action

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

pip uninstall sqiul83

What this malware does

During installation of the source package, it attempts to silently download and start a remote executable. At the time of analysis, the downloading link did not work.

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

Campaign: 2025-06-sqiul83

Reasons (based on the campaign):

Downloads and executes a remote executable.

Malicious versions

1 flagged

1.0

Indicators of compromise (SHA-256)

50965ee545a6046ec692a3500739f8584d8f7980afc4793e561c07f2eda79122

c814029b088c2f3c40eae7fa25825a2591291fe9b69892dbe3963c9645d3951f

67d309c2d4c740426c07cc17768f6313eebd765242e7e4a63aa04213d21358ea

dbf605a93475074ca3af17c25463149da08e83159a9d964bf50e0bc23fb60699

4a13c955892bb0535eba365176c353b4ecfe60d828b3f9fd5210ac7325757884

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

Campaign

RLMA-2025-036952025-06-sqiul83RLUA-2026-00778

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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