What is scan-suspicious-files?

A Windows file-system scan for suspicious files and possible malware indicators in temporary, download, startup, application-data, system, and driver folders.

Use it to examine common Windows malware locations, including startup folders, scheduled-task storage, temporary directories, Downloads, Desktop, and system driver folders.

It gives security checks a defined set of high-risk locations to inspect for unwanted files or changes.

scan-suspicious-files — Command by DeepBitsTechnology

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/scan-suspicious-files

Clone the repo

git clone --depth 1 https://github.com/DeepBitsTechnology/claude-plugins

Per session 16 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,206 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.

Model	Per session	Once invoked
Fable 5	$0.00016	$0.01206
Opus 5	$0.00008	$0.00603
Sonnet 5	$0.00003	$0.00241
Haiku 4.5	$0.00002	$0.00121

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

Security

Grade A, and why

scan-suspicious-files 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/scan-suspicious-files.md · 178 lines

How it starts

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

Suspicious File System Scan

Scan the local file system for suspicious files, malware indicators, and unauthorized modifications.

Target Directories

High-Risk Locations

%TEMP%                                    - Temporary files directory
%TMP%                                     - Alternative temp directory
%APPDATA%                                 - Application data
%LOCALAPPDATA%                            - Local application data
%PROGRAMDATA%                             - Program data (shared)
%USERPROFILE%\Downloads                   - Downloads folder
%USERPROFILE%\Desktop                     - Desktop
C:\Users\Public                           - Public user directory
C:\Windows\Temp                           - System temp directory
C:\Windows\System32\Tasks                 - Scheduled tasks

Additional Locations

%APPDATA%\Microsoft\Windows\Start Menu\Programs\Startup
%PROGRAMDATA%\Microsoft\Windows\Start Menu\Programs\Startup
C:\Windows\System32\drivers                - Kernel drivers
C:\Windows\SysWOW64                        - 32-bit on 64-bit system

Scan Criteria

Suspicious File Characteristics

1. File Extensions

Look for executables and scripts:

.exe, .dll, .sys, .scr
.bat, .cmd, .ps1, .vbs, .js
.com, .pif
Double extensions (e.g., document.pdf.exe)

2. Recently Modified Files

Files created/modified in last 7 days
Unexpected modification times (e.g., 3 AM)

3. Hidden or System Attributes

Get-ChildItem -Hidden -System -Recurse

4. Suspicious Names

Random character names (e.g., asdfjkl.exe)
System name impersonation (e.g., svch0st.exe, chr0me.exe)
Generic names (e.g., update.exe, install.exe, setup.exe)

5. Unsigned Executables

Get-AuthenticodeSignature *.exe | Where-Object {$_.Status -ne 'Valid'}

6. Large Files in Temp

Executables >10MB in temp directories
Archives in unusual locations

Analysis Process

Read the full file on GitHub · 178 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.

2d ago First seen · 178 lines · 16 tokens per session scan A 4fc207e45999

Subscribe to this mod's changes

scan-suspicious-files is a command published in the GitHub repository DeepBitsTechnology/claude-plugins (47 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 16 tokens to every session and 1,206 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.

Planning binary-analysis claude-code-plugin cybersecurity-tools incident-response malware-analysis vulnerability-assessment

scan-suspicious-files