scope-token-fetch-vectorPyPI
Advisory published Updated
scope-token-fetch-vector is a confirmed malicious PyPI package (MAL-2026-20302) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.0.0.post1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in scope-token-fetch-vector (PyPI)
What this malware does
scope_token_fetch_vector 1.0.0.post1 ships an sdist whose setup.py, on a default pip install, issues a POST to https://package-registry-receiver-stg.depx-research-bf0.workers.dev/api/pings carrying installer-side identifiers collected via getpass.getuser(), socket.gethostname(), and os.getcwd(). The destination is a non-publisher Cloudflare Workers host, the request is unconditional at build time, and the installer has no opportunity to opt in or disable it. The package self-describes this behavior as a 'dependency-confusion canary,' but the self-label does not change that installer username, hostname, and working-directory path leave the host to an author-controlled endpoint on install.
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
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for scope-token-fetch-vector (2 malicious versions).
If you installed it — respond
scope-token-fetch-vector 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 scope-token-fetch-vector 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
Campaign
References
Credits
- Amazon Inspector · finder
- Kamil Mańkowski (kam193) · reporter
Detect & block this
O3 blocks scope-token-fetch-vector-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.