Which versions of orion-algo-extrapol are malicious?

The following PyPI versions of orion-algo-extrapol are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate orion-algo-extrapol if I installed it?

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

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

Yes — orion-algo-extrapol is associated with the RLMA-2024-11107, GENERIC-standard-pypi-install-pentest, RLUA-2026-00573 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 orion-algo-extrapol 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 orion-algo-extrapol (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 orion-algo-extrapol across your stack and pipelines.

Malicious package

orion-algo-extrapolPyPI

Malicious code in orion-algo-extrapol (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-11651

Immediate action

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

pip uninstall orion-algo-extrapol

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)

1e238de84884c33f311473f6a291acb0a523897f6b1e4cf944d2a25e4139f466

0a5710a1b944dbb2e3c03b317b642cb77205c44232747033ac4c0ba6af767aee

746265a1e23f0f71fc8f64babb2fed09f5737a4a323d309c2087e90dacfa2b73

42f5245aa3b149adedb54db22ec2c775a5f0fa840937e4df3828e2d521f578b8

0bc31c9815f81ea8c3f26b24985fc61f188f4aef6d6f93e68c5b2591abf36ac4

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 orion-algo-extrapol (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 orion-algo-extrapol across your stack and pipelines.
If you installed it — respond
orion-algo-extrapol 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 orion-algo-extrapol 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 orion-algo-extrapol 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. orion-algo-extrapol 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-11107GENERIC-standard-pypi-install-pentestRLUA-2026-00573

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks orion-algo-extrapol-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