Which versions of stdid-nyxprobe are malicious?

The following PyPI versions of stdid-nyxprobe are flagged malicious: 0.0.1, 0.0.2. Treat any of these as compromised.

How do I remediate stdid-nyxprobe if I installed it?

stdid-nyxprobe 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.

I already installed stdid-nyxprobe — how do I know if it already compromised me?

If stdid-nyxprobe 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.

Is stdid-nyxprobe part of a known attack campaign?

Yes — stdid-nyxprobe is associated with the GENERIC-standard-pypi-install-pentest, IN-MAL-2026-022422, IN-MAL-2026-022445 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find stdid-nyxprobe across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for stdid-nyxprobe (2 malicious versions).

Malicious package

stdid-nyxprobePyPI

Advisory published Oct 30, 2026Updated Oct 30, 2026

stdid-nyxprobe is a confirmed malicious PyPI package (MAL-2026-18406) that steals credentials and exfiltrates sensitive data (malicious versions 0.0.1, 0.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in stdid-nyxprobe (PyPI)

MAL-2026-18406

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

pip uninstall stdid-nyxprobe

What this malware does

The package installs stdid_nyxprobe.pth into site-packages, whose sole content is import stdid_nyxprobe._beacon. Python's site.py mechanism evaluates this on every interpreter start after pip install, with no user-initiated import required. The imported module stdid_nyxprobe/_beacon.py collects host identifiers — hostname (socket.gethostname), LAN IP (via hostname -I), username (getpass.getuser), current working directory, and Python version — and POSTs them to https://api.telegram.org/bot<token>/sendMessage using a hardcoded bot token (8984095380:AAHN...) and two hardcoded chat IDs (1841775463, -5380294525). A sentinel file at ~/.cache/.stdid_beacon_fired is written to suppress repeat beacons. The package has no documented legitimate functionality that would justify this behavior; the.pth auto-exec primitive is being used purely as a persistence/auto-trigger vector for the exfiltration payload.

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

2 flagged

0.0.10.0.2

Indicators of compromise (SHA-256)

0178d6c7a642f90327546548a88f64bd17da5aa97e519249f515c0e6232c73f1

2ccf3f03f309715ca11fb3863aa89a57d4c0550606cb17839bfff9b5dfd34687

bc11a41bf569b62e65aa2a2913e3659c51a97ea1798c09e4d3ecef58add76e52

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for stdid-nyxprobe (2 malicious versions).
If you installed it — respond
stdid-nyxprobe 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 stdid-nyxprobe 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

No. stdid-nyxprobe on PyPI has been identified as a malicious package (versions 0.0.1, 0.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GENERIC-standard-pypi-install-pentestIN-MAL-2026-022422IN-MAL-2026-022445

References

Credits

Amazon Inspector · finder
Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks stdid-nyxprobe-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database