Which versions of xuiniadb are malicious?

The following PyPI versions of xuiniadb are flagged malicious: 1, 1.0, 1.1, 1.2, 1.3, 1.4, 1.5, 1.6, 1.7, 1.8. Treat any of these as compromised.

How do I remediate xuiniadb if I installed it?

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

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

Yes — xuiniadb is associated with the RLMA-2025-01259, RLMA-2026-00939 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 xuiniadb across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for xuiniadb (10 malicious versions).

Malicious package

xuiniadbPyPI

Advisory published Mar 3, 2025Updated Mar 19, 2026

xuiniadb is a confirmed malicious PyPI package (MAL-2025-2013) that executes malicious code on install (malicious versions 1, 1.0, 1.1…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in xuiniadb (PyPI)

MAL-2025-2013

Immediate action

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

pip uninstall xuiniadb

Malicious versions

10 flagged

11.01.11.21.31.41.51.61.71.8

Indicators of compromise (SHA-256)

f8318205f0ea71e6568999c1cc68b436a2bea222f4039021f077230588b57fae

2a7df9fba3a17ce2d90f31755c0833099e6bb7927b83333ed2b61fe050f021a1

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for xuiniadb (10 malicious versions).
If you installed it — respond
Remove xuiniadb 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 xuiniadb 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. xuiniadb on PyPI has been identified as a malicious package (versions 1, 1.0, 1.1, 1.2, 1.3, 1.4, 1.5, 1.6, and 2 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-01259RLMA-2026-00939

Credits

ReversingLabs · finder

Detect & block this

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