Which versions of asurion are malicious?

The following PyPI versions of asurion are flagged malicious: 99.0.0. Treat any of these as compromised.

How do I remediate asurion if I installed it?

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

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

Yes — asurion is associated with the GENERIC-standard-pypi-install-pentest, IN-MAL-2026-021532 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 asurion across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for asurion (version 99.0.0).

Malicious package

asurionPyPI

Advisory published Oct 19, 2026Updated Oct 20, 2026

asurion is a confirmed malicious PyPI package (MAL-2026-18045) that steals credentials and exfiltrates sensitive data (malicious version 99.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in asurion (PyPI)

MAL-2026-18045

Immediate action

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

pip uninstall asurion

What this malware does

setup.py executes at pip install time and POSTs a JSON payload containing the full os.environ dictionary along with hostname, username, current working directory, and platform details to the hardcoded endpoint https://webhook.site/b2967b0a-1b24-4670-8ae1-e09e3cf272c4 via urllib.request. Environment variables on developer and CI hosts routinely contain credential-grade secrets (AWS_SECRET_ACCESS_KEY, GITHUB_TOKEN, NPM_TOKEN, database passwords, cloud session tokens), so this install-time beacon is a bulk credential-sweep. The package name, implausibly high version number, and single webhook.site exfil destination are consistent with a dependency-confusion canary/exfil payload targeting an internal asurion namespace.

Installing the package or importing the module exfiltrates basic information about the host, and the package 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: GENERIC-standard-pypi-install-pentest

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

1 flagged

99.0.0

Indicators of compromise (SHA-256)

05820dd77e1f73d1a01797af6f10c6fa4ae22038be3fcd6a8cbd8c117cf6436c

393ccbeed4c71a6a21a3a697f0809845dddec09ddc8884662f40e2b2257a28a9

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for asurion (version 99.0.0).
If you installed it — respond
asurion 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 asurion 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. asurion on PyPI has been identified as a malicious package (version 99.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GENERIC-standard-pypi-install-pentestIN-MAL-2026-021532

References

Credits

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

Detect & block this

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

Explore

All malware advisories How O3 detects malware Vulnerability database