Which versions of innostage are malicious?

The following PyPI versions of innostage are flagged malicious: 7.0.1, 7.0.2, 7.0.3, 7.0.4, 7.0.6, 7.0.7. Treat any of these as compromised.

How do I remediate innostage if I installed it?

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

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

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

Malicious package

innostagePyPI

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

MAL-2024-9266

Immediate action

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

pip uninstall innostage

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

6 flagged

7.0.17.0.27.0.37.0.47.0.67.0.7

Indicators of compromise (SHA-256)

886e7758718d528adb49fb8a7362fdd0049dec6ceb7c427ff267dd94f779d126

ec433c9a241ed7127dc5d6f55b002e94a2407ddd47000e50355f118536e9021e

e92b859a44c332a5fcf2a1a7f65a7b0cadf98bb193a0836e48a1d415d19f89ad

f37b48cfd80852aed045b3839818abfc01b777dcd9256282ddb88543ece98ec8

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 (6 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging innostage across your stack and pipelines.
If you installed it — respond
innostage 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 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 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 on PyPI has been identified as a malicious package (versions 7.0.1, 7.0.2, 7.0.3, 7.0.4, 7.0.6, 7.0.7 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-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