Which versions of innostage-group are malicious?

The following PyPI versions of innostage-group are flagged malicious: 7.0.4, 7.0.6. Treat any of these as compromised.

How do I remediate innostage-group if I installed it?

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

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

Yes — innostage-group is associated with the 2024-10-innostage 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 innostage-group 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 innostage-group (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging innostage-group across your stack and pipelines.

Malicious package

innostage-groupPyPI

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

MAL-2024-9267

Immediate action

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

pip uninstall innostage-group

What this malware does

The package contains code to download and execute a reverse shell script.

When imported, the package download and runs a remote stage - a reverse shell. To mask activity, the remote domain is made to mimic PyPI host: files[.]pythonhosted[.]ru

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

Campaign: 2024-10-innostage

Reasons (based on the campaign):

The package contains code to create a reverse shell, allowing an attacker to execute any commands on the victim's machine.

Malicious versions

2 flagged

7.0.47.0.6

Indicators of compromise (SHA-256)

be4829261695d32dc7154a71a5e1b6fddce08ec803e5be38bce696de355fa6b8

9d0f2f6104de4772268a20f51e009797c0c4b0740d18d98d730417fdafdfb052

809be69022331a1464667b08db8948c477f8f014034c04261c267f8359be5253

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

Campaign

2024-10-innostage

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
Stacklok: trustypkg.dev · finder

Detect & block this

O3 blocks innostage-group-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