Which versions of sol-structs are malicious?

The following PyPI versions of sol-structs are flagged malicious: 1.0.2, 1.0.3. Treat any of these as compromised.

How do I remediate sol-structs if I installed it?

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

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

Yes — sol-structs is associated with the RLMA-2024-09286, spl-types-rentry-2024-07, RLUA-2026-00765 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 sol-structs 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 sol-structs (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging sol-structs across your stack and pipelines.

Malicious package

sol-structsPyPI

Malicious code in sol-structs (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-10161

Immediate action

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

pip uninstall sol-structs

What this malware does

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

Campaign: spl-types-rentry-2024-07

Reasons (based on the campaign):

infostealer
crypto-related

Malicious versions

2 flagged

1.0.21.0.3

Indicators of compromise (SHA-256)

6736e4c224534022f9605b156c6a9249679abbf88244b87e423d8fea97806bcd

4995e5c52f09796cdb8d2d3790f9656d1ac15f752e7bcb2c3c4dadd2064f0a67

6d466f5d94859498aa97e45fc82060c447a3004b4ea16e620a3fcc58ed8cfb3e

497085a0fac52c8a5a522339081994f343c7361c5f672d73fb724e3e8546b88a

312e73c279b27084708b9a26ec731682635d841ca4b11a8914e3dab0347adff4

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

Campaign

RLMA-2024-09286spl-types-rentry-2024-07RLUA-2026-00765

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks sol-structs-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