Version 1.0.0.post1 of the delta-nested-filter-tracer PyPI package sent the installer's identity to an external server at install time.
The package has no real code. Its only job is an install script that reports who installed it. Computers and CI runners that installed it sent their identity to an external server.
What happened
The package's install script runs during pip install and phones home.
- It collected the username, hostname and working directory of the machine installing it.
- It posted that data to
package-registry-receiver-stg.depx-research-bf0.workers.dev/api/pings. - The payload carried the label
dependency-confusion-canary-executedand a fixed event id. - It hid install errors by printing them and moving on.
Vigilance caught version 1.0.0.post1 at 18:39 UTC on 20 November 2026, 1 minute 15 seconds after it appeared on PyPI.
Affected versions
1.0.0.post1, published 18:37 UTC on 20 November 2026, carried the beacon.1.0.0, published earlier the same day, did not.- The package ships no real module. The beacon is the whole package.
Indicators of compromise
- POST requests to
package-registry-receiver-stg.depx-research-bf0.workers.dev/api/pings. - Event id
7546f936-3a64-4110-9619-da62ede34a18in the request body.
How to check
Use a shell outside the affected environment.
pip show delta-nested-filter-tracer
Also check CI build logs and dependency logs for installs of this package. PyPI no longer serves the files, so a clean install today cannot rule out earlier exposure.
What to do now
- Remove the package from your requirements and lockfile.
- Treat the username, hostname and directory it reported as leaked, and review who that exposes.
- Check your proxy or firewall logs for requests to the receiver address.
What Vigilance would show
These examples show an install hold and the corresponding owner report.
Example install message
Vigilance blocked `delta-nested-filter-tracer` 1.0.0.post1. This version is too new or changed in a way Vigilance must check first.
Example owner report
Bad update
delta-nested-filter-tracer 1.0.0.post1
Profiles whoever installs it and sends the username, hostname and working directory to a fixed address.
No security team? See who reads the alert.
Frequently asked questions
What did the package send?
The username, hostname and working directory of the machine that installed it, posted to an external server.
Which version is affected?
1.0.0.post1. The comparison record shows 1.0.0 without the beacon.
Is the package still on PyPI?
PyPI no longer serves the files for either version.
Sources
Send this page to the person who looks after AI at your company.