Detection / Experimental

Velociraptor as an Unusual Security Control and C2 Research Topic

A research-oriented look at how a legitimate endpoint visibility platform can create interesting security boundaries when its capabilities are repurposed or abused.

Published 2026-08-28·13 min·Advanced

Executive Summary

Security tools are trusted because they are useful. That trust can become a research question when legitimate remote-management or collection capabilities overlap with behaviors associated with command and control.

Developer → Repository → CI/CD → Identity → Infrastructure ↓ Evidence & Logs ↓ Detection / Defense

Executive Summary

This investigation treats Velociraptor as a research subject rather than assuming that a security tool is inherently benign or malicious. The focus is on capabilities, trust and observable behavior.

Research Question

Which capabilities create meaningful security boundaries, and what telemetry distinguishes authorized collection from suspicious repurposing?

Technical Analysis

Map the client-server relationship, artifact execution model, administrative permissions and network communication. Keep experiments isolated to controlled infrastructure.

Detection

Compare expected administrative activity with unusual execution context, network destinations, timing and operator behavior.

Mitigation

Restrict administrative access, segment management infrastructure, monitor tool deployment and preserve audit evidence for high-privilege operations.

Reproduction Lab

This investigation can be explored through the corresponding controlled laboratory where applicable. Keep all experimentation within systems you own or are explicitly authorized to test.

Explore the laboratories →

Further Research

What changes when the attacker has less privilege? Which assumptions can be tested independently? What evidence survives when the environment is rebuilt? These are the questions that turn a demonstration into research.