Which versions of httpsmovements are malicious?

The following PyPI versions of httpsmovements are flagged malicious: 1.3.5. Treat any of these as compromised.

How do I remediate httpsmovements if I installed it?

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

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

Yes — httpsmovements is associated with the RLMA-2024-11062, 2024-08-invokehttp, RLUA-2026-00401 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 httpsmovements 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 httpsmovements (version 1.3.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging httpsmovements across your stack and pipelines.

Malicious package

httpsmovementsPyPI

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

MAL-2024-11609

Immediate action

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

pip uninstall httpsmovements

What this malware does

In the invokehttp, the init.py contains obfuscated code attempting to download and run one of two executables. They are identified as malicious by VT and the tracks of Telegram URLs suggests attempting data exfiltration. The package itself looks like a copy of requests. In flophttp, using exactly the same obfuscation method, the infostealer is directly embeded into package code and exfiltrates data to a telegram channel.

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

Campaign: 2024-08-invokehttp

Reasons (based on the campaign):

infostealer
Downloads and executes a remote executable.
obfuscation
clones-real-package

Malicious versions

1 flagged

1.3.5

Indicators of compromise (SHA-256)

991798a68b3b1ec2732c4714352aa2570f74d9bd94d8855d508aa5e891845de8

bdc824c63f9129f794da1725fc9a2cde22acde14c8e72520ed92147608e4a989

1f6e48eea4c63cfcc19e892d140b0b70a48f1041c559effbaae92184fda61bc5

8b4769f9ecd55ed1184fa02eed9d62d0c0bb450d4ae69fe984d9b9a21120ac32

e4a35a76a3d00604da96e1000917a2dc69186a46ba3ef6aa24c28077ab2aa284

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

Campaign

RLMA-2024-110622024-08-invokehttpRLUA-2026-00401

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks httpsmovements-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