Malicious code in asurion (PyPI)

-= Per source details. Do not edit below this line.=-

Source: amazon-inspector (393ccbeed4c71a6a21a3a697f0809845dddec09ddc8884662f40e2b2257a28a9)

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.

Source: kam193 (05820dd77e1f73d1a01797af6f10c6fa4ae22038be3fcd6a8cbd8c117cf6436c)

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.