Which versions of pysolara are malicious?

The following PyPI versions of pysolara are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate pysolara if I installed it?

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

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

Yes — pysolara is associated with the RLMA-2024-11134, 2024-08-embeds-RealtekHDAudioManager, RLUA-2026-00647 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 pysolara 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 pysolara (version 0.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pysolara across your stack and pipelines.

Malicious package

pysolaraPyPI

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

MAL-2024-11677

Immediate action

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

pip uninstall pysolara

What this malware does

Importing a module starts downloading and executing an infostealer, widely identified by AV/sandboxes.

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

Campaign: 2024-08-embeds-RealtekHDAudioManager

Reasons (based on the campaign):

infostealer
Downloads and executes a remote executable.

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

b8f92eb32b02ca6a9343f5c3ffea988bd2b4e7c266942ae6196888f344068da4

26b6df03a328624fa2d7da880bdd7cd636c99991136635eff99dffec1309c3d9

349cad70487c67d06c267c1bf8200b6ffd83ae0d0d1eeb8be9b80bd93b2c154c

edf2851e69b8d34aefb90595e2b34725aae0a5cb9852d1a0c92a690e70cea224

02252733c0b85c808c8bb7c0c41a70f3c613ae188ac1a290cc1101134e87c98a

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

Campaign

RLMA-2024-111342024-08-embeds-RealtekHDAudioManagerRLUA-2026-00647

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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