Version 1.0.0 of the flo-pro-adk package on PyPI sent the installer's hostname and IP address to a webhook.site address during pip install.
Developers and CI runners who installed flo-pro-adk from the source distribution sent their machine's hostname and IP address to a fixed external address. PyPI has since removed the project.
What happened
The only release with code, 1.0.0, replaced the standard install step with a custom command. It ran when anyone ran pip install flo-pro-adk.
- The install command read the machine's hostname with
socket.gethostname()and its IP address withsocket.gethostbyname(). - It posted both, plus the package name and version, to
https://webhook.site/0ba7498d-7b1f-48b7-8628-a2b4b8d92ad3. - It wrapped the whole call in
except Exception: pass, so the install looked normal even when the report failed. - The package metadata called it a POC package. The code ran on every install with no way for the installer to opt out.
Vigilance caught version 1.0.0 at 14:19 UTC on 19 November 2026, 35 seconds after it appeared on PyPI.
Affected versions
1.0.0appeared at 14:19 UTC on 19 November 2026 and carries the beacon.0.0.0was an empty stub with no code and no beacon.- PyPI later removed the project. The registry index now returns 404.
Indicators of compromise
- Install-time network request to
https://webhook.site/0ba7498d-7b1f-48b7-8628-a2b4b8d92ad3with a JSON body holdinghostnameandip_address. - A
setup.pythat definesInstallWithBeacon(install)and setscmdclass={'install': InstallWithBeacon}.
How to check
Check your CI build logs and lockfile history for flo-pro-adk. A clean install today cannot rule out an earlier install. The package ran only from the source distribution at install time.
grep -R "flo-pro-adk" requirements*.txt Pipfile.lock poetry.lock uv.lock
If your logs show a pip install of flo-pro-adk 1.0.0 on 19 November 2026, the build host reported its hostname and IP address.
What to do now
- Check whether any host or CI job installed
flo-pro-adk. - If one did, the hostname and IP address of that host left it. Decide what that exposure means for your network.
- Remove the package and rebuild the environment from a clean package set.
What Vigilance would show
These examples show an install hold and the corresponding owner report.
Example install message
Vigilance blocked `flo-pro-adk` 1.0.0. This version is too new or changed in a way Vigilance must check first.
Example owner report
Bad update
flo-pro-adk 1.0.0
A custom install command sends the host's hostname and IP address to a fixed webhook.site address at pip install.
No security team? See who reads the alert.
Frequently asked questions
What did the flo-pro-adk package steal?
It sent the machine's hostname and IP address to a fixed webhook.site address during pip install. It did not read files or tokens.
Which versions of flo-pro-adk are affected?
Version 1.0.0, published on 19 November 2026. Version 0.0.0 was an empty stub.
Is flo-pro-adk still on PyPI?
No. PyPI removed the project, and the registry index now returns 404.
Sources
Send this page to the person who looks after AI at your company.