Which versions of avatar-handler are malicious?

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

How do I remediate avatar-handler if I installed it?

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

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

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

Malicious package

avatar-handlerPyPI

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

MAL-2025-191685

Immediate action

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

pip uninstall avatar-handler

What this malware does

Code pretending to handling downloading an image, but in fact is prepared to download and execute a Powershell script image properties. No known usage

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

Campaign: 2025-07-avatar-handler

Reasons (based on the campaign):

obfuscation
Downloads and executes a remote malicious script.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

055e12f86fabffdc9679d65d2e06abe77ff1f1f873beae66d52f14383a03749a

c3750cf8fac7fc22334d1fb416e7f3af691425c669829dcc9857abdc1384bbb7

4acc9843405411646c0e7096a60589651aa0a5b04a585a02e38ac0a7a88b868b

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 avatar-handler (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging avatar-handler across your stack and pipelines.
If you installed it — respond
avatar-handler 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 avatar-handler 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 avatar-handler 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. avatar-handler 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

2025-07-avatar-handler

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

O3 blocks avatar-handler-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