PyPI

xrfdc 2.0 Install-Time Host Beacon

Updated 16 Nov 2026 · Incident date 14 Nov 2026

xrfdc 2.0 sends the installing host name and resolved IP address to a fixed webhook.site endpoint.

The verified change is a limited host beacon in setup.py. The inspected code does not read passwords, tokens or environment variables.

What happened

A new setuptools install command exports host information.

  • It resolves the machine name to an IP address.
  • It posts those values with the package name and version.
  • It suppresses network errors and then continues installation.

Vigilance caught version 2.0 at 08:59 UTC on 14 November 2026, 49 seconds after it went up on PyPI. The time to catch was 49 seconds. The Aikido malware list names this attack and shows no date. Vigilance does not count this catch as first.

Affected versions

  • The inspected 2.0 source archive contains the hook.
  • The recorded prior archive, 0.0.0, has no equivalent hook. The public advisory lists both versions.

Indicators of compromise

  • setup.py class InstallWithBeacon
  • webhook.site/0fb8a38d-80f7-4134-8eb4-e5012b816090

How to check

Check package metadata without importing or installing it.

pip show xrfdc

A package listing alone does not establish that its source-install hook ran.

What to do now

  1. Remove this package from affected dependency manifests.
  2. Replace it with a reviewed dependency that your application requires.
  3. Review source-install and network logs for this endpoint.
  4. Check the installed files before deciding whether further incident response is needed.

What Vigilance would show

Vigilance checks each update before it installs. This is what a customer sees, rebuilt from the facts on this page.

On the computer, at install

Vigilance blocked `xrfdc` 2.0. This version is too new or changed in a way Vigilance must check first.

In the owner report

Bad update

xrfdc 2.0

This update now runs a command on its own when it is installed, downloads from the internet and profiles this machine and its user. The version before it did not.

Frequently asked questions

Does this prove credential theft?

No. The verified hook sends host and package information. It does not demonstrate credential theft or arbitrary remote execution.

Sources

  1. osv.dev/vulnerability/MAL-2026-19932
  2. bad-packages.kam193.eu/pypi/package/xrfdc/

More supply chain attacks

All 145 attacks in the library · What is a supply chain attack? · How to prevent supply chain attacks

Check the next update before you install it

Vigilance compares the version you trust with the new one. It names the one file that gained a power the old version did not have.

Start the free 14-day trialBrowse the attack library