Which versions of assaulthimars are malicious?

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

How do I remediate assaulthimars if I installed it?

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

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

Yes — assaulthimars is associated with the RLMA-2024-10975, 2024-08-invokehttp, RLUA-2026-00081 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 assaulthimars 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 assaulthimars (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 assaulthimars across your stack and pipelines.

Malicious package

assaulthimarsPyPI

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

MAL-2024-11531

Immediate action

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

pip uninstall assaulthimars

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)

a8a7c233d4688f85c4b2013676b778073750c92c468a6de285098eb4b87bbd8b

1a68ea4b2a210d9b8f3c2623e79c13afbfdd0d4e8048ff6237fbc512199ba063

7c588101b33f530e5b4d8504f4a9cf1353eec7356231e9f4137ab1a187b780d5

1ed57ac11dcce174b3b2159387fe855b725aa4e8c2cf03e825180d15b2820cc5

be53896622cb9e477082d20709210e868a90c1a443f1352c9142c0fee8fe4ba8

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 assaulthimars (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 assaulthimars across your stack and pipelines.
If you installed it — respond
assaulthimars 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 assaulthimars 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 assaulthimars 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. assaulthimars 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-109752024-08-invokehttpRLUA-2026-00081

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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