Interactive simulation. Mock data, no functional backend, no deployable code. Built to study detection, not to operate.

Research & publications

Frontier Labs is the umbrella; Novich0k is the flagship track. This page carries the rest of the lab's work and the citable record of it.

VileBlood: process fragmentation

A companion track in endpoint research: if an implant's duties never live in one process, no single memory image tells the whole story.

The concept. Endpoint detection correlates behavior within a process: memory content, API calls, network activity. VileBlood models an implant fragmented into three isolated processes (Network, Crypto, Execution), each holding minimal privileges and only its own slice of state, communicating over local-only channels with per-boot ephemeral keys.

Why it matters. Memory scanning finds a network client with no keys, a crypto worker with no network, or an executor with neither. The forensic whole exists nowhere at once.

FULL ANALYSIS · Read the Vileblood research page · Original Medium article

Detection counterpart

Fragmentation trades memory visibility for relationship visibility. Cross-process correlation (three same-user processes born together,, exchanging local procedure calls in lockstep) is itself a signal. Handle analysis, ALPC monitoring, and parent-child timing make the fragments legible as a set. The evasion moves the defender's unit of analysis from the process to the relationship graph.

Code

The GitHub profile hosts research tooling: analysis and detection-support frameworks. Consistent with this site's scope discipline, no deployable C2 artifacts are published or linked anywhere on this site.