Hacking on Medium
Microsoft Released the Patch For PrintNightmare vulnerability. — CyberWorkx

Microsoft has released the patch for the printNightMare vulnerability which has really created a Nightmare for the organizations.

Continue reading on Medium »

Hacking on Medium
Más de 200 empresas afectadas por ransomware en un ataque a la cadena de provisión #KaseyaVSA.

https://cdn-images-1.medium.com/max/768/0*S4jbhWahechYVg94
POR EHACKING

Continue reading on Medium »

Hacking on Medium
Microsoft’s PrintNightMare Emergency Patch Can Be Bypassed. — CyberWorkx

As we all know how the PrintNightMare bug has made a huge NightMare for IT admins and Security teams , Luckily When Microsoft had released…

Continue reading on Medium »

Hacking on Medium
HOW TO GET STARTED (REALLY STARTED) IN HACKING

https://cdn-images-1.medium.com/max/600/0*XoBXlMq5HpFUTw0D.png
By: HTMLhacker

Continue reading on Medium »

FindObjects-BOF - A Cobalt Strike Beacon Object File (BOF) Project Which Uses Direct System Calls To Enumerate Processes For Specific Loaded Modules Or Process Handles

A Cobalt Strike Beacon Object File (BOF) project which uses direct system calls to enumerate processes for specific modules or process handles.What is this repository for? Use direct systems calls within Beacon Object files to enumerate processes for specific loaded modules (e.g. winhttp.dll, amsi.dll or clr.dll). Use direct systems calls within Beacon Object files to enumerate processes for specific process handles (e.g. lsass.exe). Avoid using the Windows and Native APIs as much as possible (to avoid userland hooks). Execute this code within the beacon process using Beacon object files to avoid fork&run. Why do i need this? Utilizing direct systems calls via inline assembly in BOF code provides a more opsec safe way of interacting with the system. Using direct system calls avoids AV/EDR software intercepting user-mode API calls. The FindModule bof can be used to identify processes which have a certain module loaded, for example the .NET runtime clr.dll or the winhttp.dll module. This information can be used to select a more opsec safe spawnto candidate when using Cobalt Strike's execute-assembly or before injecting an exfill beacon shellcode using the shinject command. The FindProcHandle bof can be used to identify processes with a specific process handle in use, for example processes using a handle to the lsass.exe process. If there's a process within the system with a lsass.exe process handle, we could use this existing process/handle to read or write memory without opening a new process handle. This bypasses certain AV/EDR's capabilities of detecting and blocking LSASS process/memory access. How do I set this up? We will not supply compiled binaries. You will have to do this yourself: Clone this repository. Make sure you have the Mingw-w64 compiler installed. On Mac OSX for example, you can use the ports collection to install Mingw-w64 (sudo port install mingw-w64). Run the make command to compile the Beacon object file. Within Cobalt Strike use the Script Manager to load the FindObjects.cna script. Within a Cobalt Strike beacon context use the FindProcHandle or FindModule command with the required parameters (e.g. module or process name). Download FindObjects-BOF
Read more...

hacking: security in practice
Does anyone have a download for Ice IX?

-11-

dm on discord if you have a version, im also looking for a copy of Zeus. My discord is "#8537Deadpoppin"

submitted by /u/PMsweden
[link] [comments]

Resources to train an amazing hacker — Part 2
https://thexssrat.medium.com/resources-to-train-an-amazing-hacker-part-2-90a5814f7e3c?source=rss------bug_bounty-5

In this chapter we will go deeper into hacking resourcesContinue reading on Medium » (https://thexssrat.medium.com/resources-to-train-an-amazing-hacker-part-2-90a5814f7e3c?source=rss------bug_bounty-5)

Any African-American physical penetration testers?
https://www.reddit.com/r/Pentesting/comments/oft56q/any_africanamerican_physical_penetration_testers/

<!-- SC_OFF -->I've been listening to the Darknet Diaries episodes on physical penetration testers and it seems like there's a few intense moments with police but officers usually end up very curious rather than aggressive. I was wondering if there were any phys-pen professionals who were African-American and what their experiences were like in this field since for the general population, it seems that officers are generally more aggressive towards black people in America. <!-- SC_ON --> submitted by /u/B00OBSMOLA (https://www.reddit.com/user/B00OBSMOLA)
[link] (https://www.reddit.com/r/Pentesting/comments/oft56q/any_africanamerican_physical_penetration_testers/) [comments] (https://www.reddit.com/r/Pentesting/comments/oft56q/any_africanamerican_physical_penetration_testers/)

FindObjects-BOF - A Cobalt Strike Beacon Object File (BOF) Project Which Uses Direct System Calls To Enumerate Processes For Specific Loaded Modules Or Process Handles
http://www.kitploit.com/2021/07/findobjects-bof-cobalt-strike-beacon.html

A Cobalt Strike (https://www.kitploit.com/search/label/Cobalt%20Strike) Beacon Object File (BOF) project which uses direct system calls (https://outflank.nl/blog/2019/06/19/red-team-tactics-combining-direct-system-calls-and-srdi-to-bypass-av-edr/) to enumerate processes for specific modules or process handles.
What is this repository for?
Use direct systems calls within Beacon Object files to enumerate processes for specific loaded modules (e.g. winhttp.dll, amsi.dll or clr.dll). Use direct systems calls within Beacon Object files to enumerate processes for specific process handles (e.g. lsass.exe). Avoid using the Windows (https://www.kitploit.com/search/label/Windows) and Native APIs as much as possible (to avoid userland (https://www.kitploit.com/search/label/UserLAnd) hooks). Execute this code within the beacon process using Beacon object files (https://www.cobaltstrike.com/help-beacon-object-files) to avoid fork&run.
Why do i need this?
Utilizing direct systems calls via inline (https://outflank.nl/blog/2020/12/26/direct-syscalls-in-beacon-object-files/)assembly (https://www.kitploit.com/search/label/Assembly) in BOF code provides a more opsec safe way of interacting with the system. Using direct system calls avoids AV/EDR software intercepting user-mode API calls. The FindModule bof can be used to identify processes which have a certain module loaded, for example the .NET runtime clr.dll or the winhttp.dll module. This information can be used to select a more opsec safe spawnto candidate when using Cobalt Strike's execute-assembly or before injecting an exfill beacon shellcode using the shinject command.

The FindProcHandle bof can be used to identify processes with a specific process handle in use, for example processes using a handle to the lsass.exe process. If there's a process within the system with a lsass.exe process handle, we could use this existing process/handle to read or write memory without opening a new process handle. This bypasses certain AV/EDR's capabilities of detecting and blocking LSASS process/memory access.

How do I set this up?
We will not supply compiled binaries. You will have to do this yourself: Clone this repository. Make sure you have the Mingw-w64 compiler (https://www.kitploit.com/search/label/Compiler) installed. On Mac OSX for example, you can use the ports collection to install Mingw-w64 (sudo port install mingw-w64). Run the make command to compile the Beacon object file. Within Cobalt Strike use the Script Manager to load the FindObjects.cna script. Within a Cobalt Strike beacon context use the FindProcHandle or FindModule command with the required parameters (e.g. module or process name).

Download FindObjects-BOF (https://github.com/outflanknl/FindObjects-BOF)