Which versions of hijiko-pilaka are malicious?

The following PyPI versions of hijiko-pilaka are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate hijiko-pilaka if I installed it?

Remove hijiko-pilaka from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed hijiko-pilaka — how do I know if it already compromised me?

If hijiko-pilaka was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is hijiko-pilaka part of a known attack campaign?

Yes — hijiko-pilaka is associated with the 2026-10-vacsdk 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 hijiko-pilaka across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for hijiko-pilaka (version 1.0.0).

Malicious package

hijiko-pilakaPyPI

Advisory published Oct 20, 2026Updated Oct 20, 2026

hijiko-pilaka is a confirmed malicious PyPI package (MAL-2026-18111) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in hijiko-pilaka (PyPI)

MAL-2026-18111

Immediate action

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

pip uninstall hijiko-pilaka

What this malware does

The package uses fake http-downloaded dependencies to track downloads, and has no other purpose.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: 2026-10-vacsdk

Reasons (based on the campaign):

dependency-confusion

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

1ca95d97923a23c0fd145b6cc4def7910fa36f1b4c4e5e3cf40e5bab8c9e250d

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for hijiko-pilaka (version 1.0.0).
If you installed it — respond
Remove hijiko-pilaka from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If hijiko-pilaka was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. hijiko-pilaka on PyPI has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-10-vacsdk

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks hijiko-pilaka-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database