Which versions of assulthimars are malicious?

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

How do I remediate assulthimars if I installed it?

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

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

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

Malicious package

assulthimarsPyPI

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

MAL-2024-11532

Immediate action

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

pip uninstall assulthimars

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)

07899165f9a7ce3649471cf600fb7fcf259d370f14a9a322b5bd2d4637ba2700

9ff853d0107a12f857db92cae074b9570a5fe7eb948de192fdf662b63c86c2e5

86723cbd5b75cbf26ac4ec2f1dc722c282d7f2df07909a7d7a4ee4c07819d3bd

6c2cd6b8ba0877ae93fd62a28c3d1c5197cdb2f7398fcea09e65e848ec5681d6

62fc01dab4852cfc98cb0a667ce79013019d118c32ea4f5f49f2735b36b49470

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

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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