check-network

A network-security check for viewing active connections, listening ports, and the programs using them, then looking for suspicious activity.

In plain words
What is it for?
Inspecting TCP connections, finding listening ports, mapping connections to processes, and checking services exposed on all network interfaces.
Why use it?
It helps reveal unexpected network communication or services that may indicate malware or an exposed system service.

Command

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/deepbitstechnology/claude-plugins/check-network
Clone the repo
git clone --depth 1 https://github.com/DeepBitsTechnology/claude-plugins
Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,624 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00012 $0.01624
Opus 5 $0.00006 $0.00812
Sonnet 5 $0.00002 $0.00325
Haiku 4.5 $0.00001 $0.00162

Measured 2d ago against content hash dbb432b18a66, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

check-network scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

drbinary-chat-plugin/commands/check-network.md · 231 lines

How it starts

The opening of the file, as written. The whole thing — 231 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Network Security Check

Analyze active network connections, listening ports, and detect suspicious network activity that may indicate malware communication.

Network Analysis Tasks

1. Active Network Connections

# All active TCP connections with process info
netstat -ano | findstr ESTABLISHED

# Get detailed connection info with process names
Get-NetTCPConnection | Select-Object LocalAddress, LocalPort, RemoteAddress, RemotePort, State, OwningProcess

2. Listening Ports

# All listening ports
netstat -ano | findstr LISTENING

# Services listening on all interfaces (0.0.0.0)
Get-NetTCPConnection -State Listen | Where-Object {$_.LocalAddress -eq '0.0.0.0'}

3. Process-to-Network Mapping

# Map connections to process names
Get-NetTCPConnection | ForEach-Object {
    $process = Get-Process -Id $_.OwningProcess -ErrorAction SilentlyContinue
    [PSCustomObject]@{
        LocalAddress = $_.LocalAddress
        LocalPort = $_.LocalPort
        RemoteAddress = $_.RemoteAddress
        RemotePort = $_.RemotePort
        State = $_.State
        ProcessId = $_.OwningProcess
        ProcessName = $process.ProcessName
        ProcessPath = $process.Path
    }
}

4. DNS Cache

# View DNS resolution cache
Get-DnsClientCache | Select-Object Entry, Data, TimeToLive

5. Firewall Rules

# Check for suspicious firewall rules
Get-NetFirewallRule | Where-Object {$_.Enabled -eq $true -and $_.Direction -eq 'Inbound'}

Suspicious Indicators

High-Risk Connections

1. Unusual Remote Ports
  • Common malware ports: 1337, 31337, 4444, 5555, 6666, 6667
  • IRC ports: 6660-6669
  • RAT ports: 1080 (socks), 3389 (RDP), 5900 (VNC)
  • Tor: 9001, 9030, 9050, 9051
2. Suspicious Remote IPs
  • Connections to unexpected countries
  • Known malicious IP ranges
  • Dynamic DNS domains
  • Recently registered domains
3. Unusual Process Behavior
  • svchost.exe - Should not make external connections (usually)
  • rundll32.exe - Suspicious if connecting to internet
  • regsvr32.exe - Should not have network activity
  • User processes from temp directories with network access
  • Unsigned processes with active connections

Read the full file on GitHub · 231 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 231 lines · 12 tokens per session scan A dbb432b18a66

Subscribe to this mod's changes

check-network is a command published in the GitHub repository DeepBitsTechnology/claude-plugins (46 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 12 tokens to every session and 1,624 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.