What does the hooktest1 malware do?

During installation, the package starts a code to retrieve and execute commands from Discord Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers. Campaign: 2025-11-hooktest1 Reasons (based on the campaign): - The package overrides the install command in setup.py to execute malicious code during installation. - The package contains code to execute remote commands (probably limited to a specific set) on the victim's machine. - rat

Which versions of hooktest1 are malicious?

The following PyPI versions of hooktest1 are flagged malicious: 0.1.0, 0.1.1. Treat any of these as compromised.

How do I remediate hooktest1 if I installed it?

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

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

Yes — hooktest1 is associated with the 2025-11-hooktest1, RLMA-2025-06569, RLUA-2026-00394 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 hooktest1 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 hooktest1 (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging hooktest1 across your stack and pipelines.

Malicious package

hooktest1PyPI

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

MAL-2025-191760

Immediate action

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

pip uninstall hooktest1

What this malware does

During installation, the package starts a code to retrieve and execute commands from Discord

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

Campaign: 2025-11-hooktest1

Reasons (based on the campaign):

The package overrides the install command in setup.py to execute malicious code during installation.
The package contains code to execute remote commands (probably limited to a specific set) on the victim's machine.
rat

Malicious versions

2 flagged

0.1.00.1.1

Indicators of compromise (SHA-256)

a5b3c9015ababfab03306c83c75f2f7b31c76874e7e591ffaf6b12b0e3b0f543

b3e91d71ab21e3575f1354593a314d50bc188b0db7b3851040e522426a765417

b74fc5669380714b07015d75eada0da20479d05867676f16bd3a507eef910c0f

299b7470e3d470e294ff376356681640cb4f6adf3dbfabfdbdad1fc47cb9b7b2

ebd6b381b33c1b8aecf0255b45a7c845de271c39fa9fb82f8109d5f87c69442c

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

Campaign

2025-11-hooktest1RLMA-2025-06569RLUA-2026-00394

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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