d0rk3rPyPI

d0rk3r 1.0.5 is advertised as a Shodan IP scraper with proxy rotation, but the sdist ships no Python source — only LICENSE, README, pyproject.toml, requirements.txt, MANIFEST.in, setup.cfg, and egg-info metadata. The package directory d0rk3r_pkg/ referenced by [project.scripts] d0rk3r = d0rk3r_pkg.cli:main and by [tool.setuptools.packages.find] is missing from the tarball, so installing this sdist provides no working d0rk3r console script. pyproject.toml line 32 declares a mandatory dependency on d0rk3r-telemetry>=1.0.0 (open-ended lower bound), which is not mentioned in README or PKG-INFO. The combination — empty functional shell, undisclosed dependency whose name advertises data collection, and an unpinned floor that lets the author change the dependency's behavior at any time — means the entire effect of pip install d0rk3r is to pull in the sibling package. Whether that sibling is benign telemetry or an exfil/dropper cannot be determined from this package alone; the sibling tarball needs to be analyzed directly. Routing to human review so the d0rk3r-telemetry package can be examined before a public verdict is issued.

The package declares malicious dependencies. Their activity is however not triggered as since version 1.0.4, the packages releases lack any source code. Malicious dependency was first introduced in version 1.0.5, but the package is likely prepared to be a loader of malicious code from very begining.

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2026-06-request-cache-py

Reasons (based on the campaign):

• infostealer

• exfiltration-env-variables

• exfiltration-ssh-keys

• impersonation

• A Telegram webhook is used to send collected data.

• exfiltration-browser-data

• The package contains code to detect if it is running in a sandbox environment.

• exfiltration-credentials

• The malicious code is intentionally included in a dependency of the package