Skip to content

Agent prompt: never run vssadmin or restore-point commands - #365

Merged
shadowbrok3r merged 1 commit into
mainfrom
fix/agent-no-shadow-copy
Oct 10, 2026
Merged

shadowbrok3r merged 1 commit into
mainfrom
fix/agent-no-shadow-copy

Conversation

@shadowbrok3r

Copy link
Copy Markdown
Owner

Summary

Agents must not run vssadmin, Checkpoint-Computer or any other restore-point or shadow-copy command, and they skip restore-point steps in procedures.

Webroot sees a shadow-copy command in MasterTech's process tree as ransomware and kills MasterTech. MasterTech is unsigned and its hash changes with every release, so Webroot always runs it as an unknown, monitored program.

On DESKTOP-VRT0DTD (QC SO 2155035), MasterTech was killed four times on 2026-10-09, at 21:50, 22:32 and 23:57 UTC, and 00:05:59 UTC on 10-10. Each time, C:\ProgramData\WRData\WRLog.log logged:

IR: A highly suspicious action was attempted: C:\Users\Owner\Desktop\MasterTech.exe

That line has the same timestamp, to the millisecond, as Webroot logging vssadmin.exe starting from an agent's restore-point check. After the last kill the exe no longer launched.

Related changes, already live

  • The active rcbottom known_bad_driver fix text no longer includes the restore-point step.
  • QC skill 1.2.1 on .7 has the same rule.

Test plan

  • New machine_sessions_never_touch_shadow_copies test.
  • cargo test -p displays --lib --no-default-features --features tokio,wasm-plugins,native-telemetry

🤖 Generated with Claude Code

Webroot treats a shadow-copy command run under MasterTech as ransomware and
kills MasterTech. On DESKTOP-VRT0DTD it killed the client four times on
2026-10-09, each the moment an agent's restore-point check started
vssadmin.exe.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@shadowbrok3r
shadowbrok3r merged commit 4fac178 into main Oct 10, 2026
10 of 16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant