Which versions of posi are malicious?

The following PyPI versions of posi are flagged malicious: 7.0.6. Treat any of these as compromised.

How do I remediate posi if I installed it?

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

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

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

Malicious package

posiPyPI

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

MAL-2024-9269

Immediate action

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

pip uninstall posi

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

1 flagged

7.0.6

Indicators of compromise (SHA-256)

48202022f68c7c68abbb49259a46356472746e1e7e5077f7933e32b7a8997aba

9eff1140edfe020fe3ef5905579f5e5d74a8cd0638332576041513ce894eb27e

9509649c045b2e10dc41d0750650abb04f99301a38aa1382460bbaddd22a3940

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