By Null Ventures MCP platform
Menu

supply chain event / NVI-00011066 / Revision 1

Malicious code in darkglitch (PyPI)

GitHub lists this malware advisory for darkglitch, darkglitch, darkglitch, darkglitch. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.

source listedactiveGHSA-qvmp-g666-g29h

This report has not inspected your inventory, configuration, deployed build, reachability or evidence. A catalog listing and a severity score do not establish exposure or compromise.

01 / Meaning

Why it matters

Published affected context helps an owner decide what evidence to gather. This report has not examined your application.

02 / Applicability

The affected context

Affected versions, configuration prerequisites and known exclusions are public. Confirm each one against the deployed service.

darkglitch

source listed
  • = 1.2.0

## Source: amazon-inspector (6d02eb8be388433532783a7bf88864824b50756b7ced4f8728721866740c5df1) darkglitch 1.2.0 ships a listener mode (`-l -c`) that opens a WebSocket connection to the hardcoded signaling host `https://malware-signal.vercel.app/` and joins the fixed room `D4RKGLI7CH`. Incoming `remote-command` messages are passed directly into `subprocess.run(command, shell=True)` inside `_execute_command`, giving any party with access to that signaling server arbitrary shell execution on the host running the listener. `core/config.py` hardcodes the host and room. The `-r/--run` mode invokes PyInstaller with `--noconsole --onefile` to build `darkglitch_listener.exe`, a windowless Windows agent whose entry point immediately calls `asyncio.run(listen_bash_mode())`, packaging the same remote-shell listener as a hidden persistent agent. The self-labeling of the host as `malware-signal.vercel.app` and the room as `D4RKGLI7CH` matches the operational shape of a remote-access trojan. --- Credit: OpenSSF ([source](https://github.com/ossf/malicious-packages/blob/49d0cfba3689ed9b195d101d3a2a964c6a77f767/osv/malicious/pypi/darkglitch/MAL-2026-10

GitHub Advisory Database

darkglitch

source listed
  • = 1.2.9

## Source: amazon-inspector (6d02eb8be388433532783a7bf88864824b50756b7ced4f8728721866740c5df1) darkglitch 1.2.0 ships a listener mode (`-l -c`) that opens a WebSocket connection to the hardcoded signaling host `https://malware-signal.vercel.app/` and joins the fixed room `D4RKGLI7CH`. Incoming `remote-command` messages are passed directly into `subprocess.run(command, shell=True)` inside `_execute_command`, giving any party with access to that signaling server arbitrary shell execution on the host running the listener. `core/config.py` hardcodes the host and room. The `-r/--run` mode invokes PyInstaller with `--noconsole --onefile` to build `darkglitch_listener.exe`, a windowless Windows agent whose entry point immediately calls `asyncio.run(listen_bash_mode())`, packaging the same remote-shell listener as a hidden persistent agent. The self-labeling of the host as `malware-signal.vercel.app` and the room as `D4RKGLI7CH` matches the operational shape of a remote-access trojan. --- Credit: OpenSSF ([source](https://github.com/ossf/malicious-packages/blob/49d0cfba3689ed9b195d101d3a2a964c6a77f767/osv/malicious/pypi/darkglitch/MAL-2026-10

GitHub Advisory Database

darkglitch

source listed
  • = 1.4.5

## Source: amazon-inspector (6d02eb8be388433532783a7bf88864824b50756b7ced4f8728721866740c5df1) darkglitch 1.2.0 ships a listener mode (`-l -c`) that opens a WebSocket connection to the hardcoded signaling host `https://malware-signal.vercel.app/` and joins the fixed room `D4RKGLI7CH`. Incoming `remote-command` messages are passed directly into `subprocess.run(command, shell=True)` inside `_execute_command`, giving any party with access to that signaling server arbitrary shell execution on the host running the listener. `core/config.py` hardcodes the host and room. The `-r/--run` mode invokes PyInstaller with `--noconsole --onefile` to build `darkglitch_listener.exe`, a windowless Windows agent whose entry point immediately calls `asyncio.run(listen_bash_mode())`, packaging the same remote-shell listener as a hidden persistent agent. The self-labeling of the host as `malware-signal.vercel.app` and the room as `D4RKGLI7CH` matches the operational shape of a remote-access trojan. --- Credit: OpenSSF ([source](https://github.com/ossf/malicious-packages/blob/49d0cfba3689ed9b195d101d3a2a964c6a77f767/osv/malicious/pypi/darkglitch/MAL-2026-10

GitHub Advisory Database

darkglitch

source listed
  • = 1.4.4

## Source: amazon-inspector (6d02eb8be388433532783a7bf88864824b50756b7ced4f8728721866740c5df1) darkglitch 1.2.0 ships a listener mode (`-l -c`) that opens a WebSocket connection to the hardcoded signaling host `https://malware-signal.vercel.app/` and joins the fixed room `D4RKGLI7CH`. Incoming `remote-command` messages are passed directly into `subprocess.run(command, shell=True)` inside `_execute_command`, giving any party with access to that signaling server arbitrary shell execution on the host running the listener. `core/config.py` hardcodes the host and room. The `-r/--run` mode invokes PyInstaller with `--noconsole --onefile` to build `darkglitch_listener.exe`, a windowless Windows agent whose entry point immediately calls `asyncio.run(listen_bash_mode())`, packaging the same remote-shell listener as a hidden persistent agent. The self-labeling of the host as `malware-signal.vercel.app` and the room as `D4RKGLI7CH` matches the operational shape of a remote-access trojan. --- Credit: OpenSSF ([source](https://github.com/ossf/malicious-packages/blob/49d0cfba3689ed9b195d101d3a2a964c6a77f767/osv/malicious/pypi/darkglitch/MAL-2026-10

GitHub Advisory Database

03 / Response

What to do next

  1. investigate

    Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.

    Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system. GitHub Advisory Database

A fixed release is not deployment evidence.

Check current vendor support and compatibility. After making a change, verify the deployed build and relevant runtime conditions. Keep the evidence, owner and time. An updated lockfile alone does not prove what is running.

04 / Limits

What this report cannot establish

  • Customer inventory, deployment, reachability and exploitation have not been inspected.
Read the collection and interpretation limits ↗

05 / Provenance

Sources you can inspect

Each assertion retains its source. Mirrored records may repeat one underlying publisher; additional links are not independent corroboration.

  1. GHSA-qvmp-g666-g29h ↗

    GitHub Advisory Database · vendor advisory

    Observed . GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.

Public revision history

Only published revisions appear here. Routine fetches do not create a material-change event.

  1. Revision 1 ·

    First indexed by Null; source disclosure date is shown separately.

Read the public revision data ↗

The next step is private

Bring the question into your environment.

The connected workflow is a development preview for inventory, contextual matching, owner decisions and evidence-based verification. No system-specific result is generated by this page.

See the synthetic workflow preview ↗