Which versions of syssqlitelibery are malicious?

The following PyPI versions of syssqlitelibery are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate syssqlitelibery if I installed it?

Remove syssqlitelibery from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed syssqlitelibery — how do I know if it already compromised me?

If syssqlitelibery was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is syssqlitelibery part of a known attack campaign?

Yes — syssqlitelibery is associated with the RLMA-2024-04892, RLUA-2024-09360 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 syssqlitelibery across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for syssqlitelibery (version 1.0.0).

Malicious package

syssqliteliberyPyPI

syssqlitelibery is a confirmed malicious PyPI package (MAL-2024-6089) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in syssqlitelibery (PyPI)

MAL-2024-6089

Immediate action

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

pip uninstall syssqlitelibery

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

cc1bc30f7a9e245cb3bc6a806bd18cf4d0989dda8642c41b40ee1afc210ad4ce

c680c41484d37a89c610928a2e6cf59a5ca6dc3f10a43b53b76190dda32c0254

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for syssqlitelibery (version 1.0.0).
If you installed it — respond
Remove syssqlitelibery from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If syssqlitelibery was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. syssqlitelibery on PyPI has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-04892RLUA-2024-09360

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks syssqlitelibery-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database