What does the hooktest3 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 hooktest3 are malicious?

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

How do I remediate hooktest3 if I installed it?

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

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

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

Malicious package

hooktest3PyPI

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

MAL-2025-191761

Immediate action

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

pip uninstall hooktest3

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

1 flagged

0.1.1

Indicators of compromise (SHA-256)

03446293baa732834900cda71b588009cb031b9ef180c0c89bf4147191eb530a

3d1104ab742749c40acd3c4c989dba15890db64fd22f688dea72727fbc5b9d23

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

Campaign

2025-11-hooktest1

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

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