Remote thread injection into a child process
injection_remote_thread
Performs the classic OpenProcess / VirtualAllocEx / WriteProcessMemory / CreateRemoteThread sequence against a child process this test starts itself, with a stub that does nothing but return. Each API call is recorded separately so the report shows which one was refused.
What it needs before it will run
-
--i-understandNeeds explicit consent: this test changes machine state or fetches real offensive tooling.
Gates are cumulative and none of them is implied by another: see the three gates for why they are separate decisions.
ATT&CK techniques it exercises
| Technique | Name | Tactic | Across public reports |
|---|---|---|---|
| T1055.001 | Dynamic-link Library Injection | Defense Evasion | coverage statistics |
| T1055.002 | Portable Executable Injection | Defense Evasion | coverage statistics |
How often anything notices
Not enough data: fewer than 3 public reports have run this test, so no rate is published for it. Groups below that threshold are withheld everywhere on the site — with one or two contributors an average is one organisation's result with a percent sign after it.
Other process injection tests
| Test | What it does | Severity |
|---|---|---|
| Dynamic linker hijacking of a child process injection_preload_env | Starts a child process with LD_PRELOAD (or DYLD_INSERT_LIBRARIES on macOS) pointing at a library in the sandbox, the standard Unix code-injection rout… | high |
| ptrace attach to a child process injection_ptrace_attach | Attaches to a child process with ptrace, reads its registers and detaches again. On Linux this is the equivalent of a debugger taking over another pro… | high |
Catalogue generated from client 0.1.0. A test's behaviour can
change between releases; this page describes the version named here.