Which versions of solaraund are malicious?

The following PyPI versions of solaraund are flagged malicious: 0.1. Treat any of these as compromised.

How do I remediate solaraund if I installed it?

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

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

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

Malicious package

solaraundPyPI

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

MAL-2024-11711

Immediate action

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

pip uninstall solaraund

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.1

Indicators of compromise (SHA-256)

c7378b2f24189fdfcbc9814614d19955b92ba0334a6940570ad0c0aaaa07197e

06a77537b89cf0809b4cfc6b7a319e296631d9f0be616f7553b9435d0cc194e8

e54b1521b270ef90ecd30f1d3a59dfcf3027ce2a7c1637d45a8ac2a6e82aa929

6d1a79c4ccb5f358f5c6a7ec310a9c09452ba9806b39de2d8b6384c415c78c8a

2a95dd17e78d9faa2a4034f4b5f1b8ee89acd4ff717377bec1762ee2b2d6c5c0

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

Campaign

RLMA-2024-111692024-08-embeds-RealtekHDAudioManagerRLUA-2026-00770

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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