Which versions of napari-ufish are malicious?

The following PyPI versions of napari-ufish are flagged malicious: 0.0.2, 0.0.3. Treat any of these as compromised.

How do I remediate napari-ufish if I installed it?

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

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

Yes — napari-ufish is associated with the 2026-06-compr-woodpecker, IN-MAL-2026-008325 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 napari-ufish 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 napari-ufish (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging napari-ufish across your stack and pipelines.

Malicious package

napari-ufishPyPI

Malicious code in napari-ufish (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-5275

Immediate action

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

pip uninstall napari-ufish

What this malware does

The package was found to contain malicious code or consuming dependency that contains malicious code

Versions 0.0.2, 0.0.3 were compromised.

Compromised packages start an obfuscated infostealer. The infostealer is a heavily obfuscated JavaScript code executed using Bun runtime on Python startup. It collectes all kinds of sensitive data, including API keys, credentials to package repositories, cryptocurrency assets, password manager data. Infostealer actively queries online services to collect additional secrets as well as attempts to gain persistence and spread further by publishing infected packages using collected credentials. Data are exfiltrated likely using Github. The code seems to threaten to wipe the user's data if it detects invalid GitHub tokens. Cleanup should be done with caution.

It seems to be related to the recent Mini Shai Hulud campaign.

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

Campaign: 2026-06-compr-woodpecker

Reasons (based on the campaign):

compromised-package
exfiltration-env-variables
exfiltration-cloud-tokens
exfiltration-credentials
abuses-pth
obfuscation
infostealer
The package contains code to detect if it is running in a sandbox environment.
exfiltration-crypto
files-exfiltration
destructive-actions

Malicious versions

2 flagged

0.0.20.0.3

Indicators of compromise (SHA-256)

08623bcaeb4e2270d7fb5bc9e4e51e338d1270b2a45188c6bddb01aa07ff32c6

5103d2b75fe554764a66f5e03957c303d4085a7d5133463f58aa0c83a87f5d7d

4537e4c888c7db13db173ca68bf6b578118b10308eb923a4625d9575a0054397

03d0f90ffc39a2887949a5f33ef6495b6d304e4ba82e78172ce7651f1366a818

0caba416a889043d4cd39d83cbb513e7169908ff9f3cdc5219575f12d7f212b4

9785bcfea6c0bd6ff8193d721e15b2a80e4e718e16bd8722d018703bbd0b2516

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

Campaign

2026-06-compr-woodpeckerIN-MAL-2026-008325

References

Credits

Amazon Inspector · finder
Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks napari-ufish-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