Which versions of stackstorm-runner-action-chain are malicious?

The following PyPI versions of stackstorm-runner-action-chain are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate stackstorm-runner-action-chain if I installed it?

stackstorm-runner-action-chain 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 stackstorm-runner-action-chain — how do I know if it already compromised me?

If stackstorm-runner-action-chain 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 stackstorm-runner-action-chain part of a known attack campaign?

Yes — stackstorm-runner-action-chain is associated with the RLMA-2024-11172, GENERIC-standard-pypi-install-pentest, RLUA-2026-00780 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 stackstorm-runner-action-chain 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 stackstorm-runner-action-chain (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging stackstorm-runner-action-chain across your stack and pipelines.

Malicious package

stackstorm-runner-action-chainPyPI

Malicious code in stackstorm-runner-action-chain (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-11714

Immediate action

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

pip uninstall stackstorm-runner-action-chain

What this malware does

Installing the package or importing the module exfiltrates basic information about the host, and the package has no other purpose.

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: GENERIC-standard-pypi-install-pentest

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.
The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

979101b65cefdc8e98f1e5ce9818063d141401a3fa70e78053dd86fe7534c39e

241b6b9ae4553c2ac293b75ccda1533cbce64d33c7b7cff3efe84796849af39d

0cc9e6be890f15ba83b67af002dc0fdec59a68ebdd2696ab5168df443ed2dabf

70fcce6ff3315b2cfa9c0f5635ad034785ef950ca98a7184689efaf7bf2e75e4

cefbeee3c89f5dd721f139f167e0cf8eab51dd1a5655b992daaab84ee86f294e

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

Campaign

RLMA-2024-11172GENERIC-standard-pypi-install-pentestRLUA-2026-00780

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks stackstorm-runner-action-chain-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