Which versions of malinssx are malicious?

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

How do I remediate malinssx if I installed it?

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

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

Yes — malinssx is associated with the RLMA-2025-03640, 2025-07-malimalo 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 malinssx 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 malinssx (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 malinssx across your stack and pipelines.

Malicious package

malinssxPyPI

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

MAL-2025-5656

Immediate action

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

pip uninstall malinssx

What this malware does

The only goal of the package is to execute a webhook or a suspicious file during installation.

Closely related to 2025-07-0x9xnx - created after previous packages were quarantined, similar names, similar usage, but no clearly malicious parts.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: 2025-07-malimalo

Reasons (based on the campaign):

The package overrides the install command in setup.py to execute malicious code during installation.

The OpenSSF Package Analysis project identified 'malinssx' @ 0.0.1 (pypi) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

3d92abafc09cf0f7dc822d1020b48ae9cef15a8844d75ec034e30a49af7de3f4

2afe87b7a6471b1348b91836990a415db226b9d0a1e5235335dcf2be39ae463e

6500e2c0d9c4841404e0518a1fe4e23f8eced03e773be53e46756b00da876f74

ec1d3e0940a3c37917b528689547d3728f9f3d0b9e408acc7dcc67435c09d2b0

da25513446adec2808388febdd965ed96d11c7563841b371c8d2fbe7788e5db4

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for malinssx (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 malinssx across your stack and pipelines.
If you installed it — respond
Remove malinssx 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 malinssx 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 malinssx 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. malinssx 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-2025-036402025-07-malimalo

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
OpenSSF: Package Analysis · finder
ReversingLabs · finder

Detect & block this

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