Which versions of iconnect are malicious?

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

How do I remediate iconnect if I installed it?

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

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

Yes — iconnect is associated with the RLMA-2025-02575, 2025-05-sl4x01 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 iconnect 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 iconnect (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 iconnect across your stack and pipelines.

Malicious package

iconnectPyPI

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

MAL-2025-3743

Immediate action

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

pip uninstall iconnect

What this malware does

Packages that seem to be created by a legit bug bounty hunter. Designed to look like created by different organisations, they contain a couple of data exfiltration (including all env variables) and potential remote code execution (though the URL seems not to serve any code).

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

Campaign: 2025-05-sl4x01

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
exfiltration-env-variables
impersonation

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

It is considered malicious because:

The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

349d4957f86b42a8d229fbb29cea197f5f303b084ee77a56188e85d00068b11e

fab534a9d3da3942edafb6abb06169d2527479cdc053d589336da2d12df35a8b

3d53f9255516c80c6d2b3fda905ff465c1438480ab334501d546b2d5230be66c

e53aae69656f138607d0de8abe11d4b48ed6156875f07ec0da7485dd776f7158

e7810f34748e81cdc4e4bf87f3632caeb1025077ef98987aeb3a596e665ceaac

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 iconnect (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 iconnect across your stack and pipelines.
If you installed it — respond
iconnect 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 iconnect 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 iconnect 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. iconnect 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-025752025-05-sl4x01

References

Credits

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

Detect & block this

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