the ghost in the wires (@nico_sec) profile picture

offensive security, red team and adversary emulation

Joined December 2018
Photo by the ghost in the wires (@nico_sec)Photo by the ghost in the wires (@nico_sec)Photo by the ghost in the wires (@nico_sec)Photo by the ghost in the wires (@nico_sec)Photo by the ghost in the wires (@nico_sec)Photo by the ghost in the wires (@nico_sec)Photo by the ghost in the wires (@nico_sec)Photo by the ghost in the wires (@nico_sec)Photo by the ghost in the wires (@nico_sec)Photo by the ghost in the wires (@nico_sec)
esse GTA VI está belíssimo.
82
que porra de pergunta é essa, irmão? cada coisa que temos de ler, tem gente que se passa
Replying to @juligaioso
acho curioso mulher em cyber... tipo, qual aspecto de cybersec iria fazer uma mulher se interessar pela area?
6
66
1,320
Curioso como eu consigo explicar coisas de cyber para meus amigos que vem tirar duvida comigo na maior segurança. Chega na hora de entrevistas, dá branco.
2
27
613
queria não ser tão sistemático no meu dia a dia. Por exemplo, se eu faço academia, nao consigo estudar e vice-versa. Se eu saio de casa um dia, nao consigo fazer mais nada no resto do dia. pqp, é foda ser mole desse jeito
2
1
19
573
Não vejo porque tanto imediatismo pra querer jogar logo GTA VI, prefiro esperar sair pra PC e jogar.
1
3
190
só queria arrumar um emprego logo, um saco ter que ficar me candidatando a mil vagas, fazer mil entrevistas e nao dar em nada
3
39
3
320
3,776
brincando no cobalt strike, agora é tentar customizar
158
Hoje foi um dia produtivo: brinquei no Mythic e testei alguns implantes
1
1
214
Vendo uma galera sendo demitida pq o chefe nao curtiu que fez o L moral da historia: nao aceitar colegas de trabalho em redes sociais.
1
141
toda hora a geng morre sempre tentando fazendo objetivo e brigando por ele kkkkkkkkkkkk
124
todo dia que faço academia, minha vontade de estudar morre
2
1
255
puta que pariu. Canyon é o melhor jg disparado da atualidade.
1
2
211
the ghost in the wires retweeted
Process Injection is one of the most fundamental capabilities of malware. It plays a role both in establishing a foothold after initial access and during post-exploitation, but the technique suffers from a fundamental problem: its traditional behavior is predictable and well understood by defensive solutions. The classic Remote Process Injection flow can be roughly summarized in four stages: 1. Enumerate processes on the compromised machine; 2. Obtain a handle to the target process; 3. Allocate and write shellcode into the target process's memory space; 4. Change the memory region's permissions from RW to RX. The set of WINAPIs designed for these operations is relatively small, which makes life easier for EDRs. The list of the most sensitive APIs is short: VirtualAllocEx → NtAllocateVirtualMemory VirtualProtectEx → NtProtectVirtualMemory WriteProcessMemory → NtWriteVirtualMemory Whether through kernel callbacks or userland hooks on ntdll, these calls are easily monitored. There are ways to deal with this problem, including simply not performing process injection, at least not during initial access, and choosing something like DLL Sideloading. But we want a challenge, right? :) In the screenshot I show something different. It is possible to write into a remote process's memory without invoking sensitive APIs such as NtAllocateVirtualMemory or NtWriteVirtualMemory. Based on an article written by the amazing researcher @TwoSevenOneT, I developed a shellcode runner that successfully evades Windows Defender (with Cloud-Delivered Protection enabled) by poisoning a target process hStdInput. The technique abuses Windows console applications (such as netsh.exe) by redirecting the child process's hStdInput handle via CreateProcess with STARTF_USESTDHANDLES. The content written to the Named Pipe ends up allocated in the target process's memory by the operating system itself, with no explicit call to VirtualAllocEx or WriteProcessMemory. To locate the shellcode in remote memory, the payload is preceded by a previously established byte sequence that serves as a marker. The runner scans the target process's memory for this pattern, identifies the region, adjusts permissions, and redirects execution to the shellcode. None of the most sensitive APIs are used for writing the payload. Three APIs that are also used, among other purposes, in traditional injection are present (VirtualProtectEx, CreateProcessW, and ResumeThread), but outside their traditional context they are far less suspicious. Currently, this shellcode runner PoC would not successfully evade top-tier EDRs, but the goal was to demonstrate viability, not perfection. A little bit more evasion tomfoolery would be enough. The link to the article that guided me through this experiment will be down below, make sure to do something useful with your life and read it. Keep Hacking, Sp1d3rM_*!^
8
33
1
273
10,305
hj to num hiperfoco fudido em estudar
1
4
282
Pior estratégia de vendas é querer vender produtos na black friday e em vez de botar o preço, colocam link pra falar com consultor de vendas. Afasta mais o cliente do que aproxima, pelo menos no meu caso
1
2
148
Mais uma entrevista pra gringa em offsec focada em AI. Vou ter que larpar.
2
33
813
Slk ainda não resolveram esse xabu da microsoft?
2
151
Será se vai ter black friday pra CRTO? Pensando aqui.
134