Hacker, security researcher, and pentester areyou1or0 explains how to setup black box fuzzers Spike, Boo-Fuzz, Boo-Gen to execute binary…Continue reading on System Weakness » (https://systemweakness.com/hack-bits-fuzzing-for-binary-exploitation-7a7e3a18eb8c?source=rss------bug_bounty-5)

Hacking on Medium
Exploiting Local File Inclusion with Python

https://cdn-images-1.medium.com/max/708/0*VvllI8VbJuSb394Z.png
Introduction

Continue reading on Medium »

Hacking on Medium
Tornado Cash Hacker Hands Back Control

https://cdn-images-1.medium.com/max/1300/1*5C4mMQXameMb8NcZUdfCog.jpeg
The Hacker who took control of Tornado Cash has given control back to the community and team, after making off with 472 Ethereum.

Continue reading on Coinmonks »

Hacking on Medium
Protecting Your Unity Games from Hacking: Best Practices and Security Tips

https://cdn-images-1.medium.com/max/900/1*89emjI_wZwp1vxMxtQcBrg.jpeg
Introduction :

Continue reading on Medium »

Hacking on Medium
Hack Bits: Fuzzing for Binary Exploitation

https://cdn-images-1.medium.com/max/2600/0*_oMx8heKKvEGQk6Y
Hacker, security researcher, and pentester areyou1or0 explains how to setup black box fuzzers Spike, Boo-Fuzz, Boo-Gen to execute binary…

Continue reading on System Weakness »

New Attack Surface tool OrgASM
https://www.reddit.com/r/Pentesting/comments/13wkn6a/new_attack_surface_tool_orgasm/

<!-- SC_OFF -->Hi ! I've created a new Attack Surface discovery tool. What do you think of it ? If anyone would like to try it out and has other ideas to implement, don't hesitate ! You can also easily add other tools after the initial scan in a very easy and modular way. I've already implemented a port scanner, a service detector with wappalyzer and a nuclei scan. github : https://github.com/ugomeguerditchian/OrgASM <!-- SC_ON --> submitted by /u/WherxitRBN (https://www.reddit.com/user/WherxitRBN)
[link] (https://www.reddit.com/r/Pentesting/comments/13wkn6a/new_attack_surface_tool_orgasm/) [comments] (https://www.reddit.com/r/Pentesting/comments/13wkn6a/new_attack_surface_tool_orgasm/)

Nidhogg - All-In-One Simple To Use Rootkit For Red Teams
http://www.kitploit.com/2023/05/nidhogg-all-in-one-simple-to-use.html

Current Features Process hiding and unhiding Process elevation Process protection (https://www.kitploit.com/search/label/Protection) (anti-kill and dumping) Bypass pe-sieve Thread hiding Thread protection (anti-kill) File protection (anti-deletion and overwriting) File hiding Registry keys and values protection (anti-deletion and overwriting) Registry keys and values hiding Querying currently protected processes, threads, files, registry keys and values Arbitrary kernel R/W Function patching Built-in AMSI bypass Built-in ETW patch Process signature (PP/PPL) modification Can be reflectively loaded Shellcode Injection APC NtCreateThreadEx DLL Injection APC NtCreateThreadEx Querying kernel callbacks ObCallbacks Process and thread creation routines Image loading routines Registry callbacks Removing and restoring kernel callbacks ETWTI tampering Reflective loading Since version v0.3, Nidhogg can be reflectively loaded with kdmapper (https://github.com/TheCruZ/kdmapper) but because PatchGuard (https://en.wikipedia.org/wiki/Kernel_Patch_Protection) will be automatically triggered if the driver registers callbacks, Nidhogg will not register any callback. Meaning, that if you are loading the driver reflectively these features will be disabled by default: Process protection Thread protection Registry operations PatchGuard triggering features These are the features known to me that will trigger PatchGuard (https://en.wikipedia.org/wiki/Kernel_Patch_Protection), you can still use them at your own risk. Process hiding File protecting Basic Usage It has a very simple usage, just include the header and get started! #include "Nidhogg.hpp"

int main() {
HANDLE hNidhogg = CreateFile(DRIVER_NAME, GENERIC_WRITE | GENERIC_READ, 0, nullptr, OPEN_EXISTING, 0, nullptr);
// ...
DWORD result = Nidhogg::ProcessUtils::NidhoggProcessProtect(pids);
// ...
} Setup Building the client To compile the client, you will need to install CMake (https://community.chocolatey.org/packages/cmake.install/3.13.1) and Visual Studio 2022 (https://visualstudio.microsoft.com/thank-you-downloading-visual-studio/?sku=Community&rel=16) installed and then just run: \Example mkdir build cd build cmake .. cmake --build ." dir="auto">cd \Example
mkdir build
cd build
cmake ..
cmake --build . Building the driver To compile the project, you will need the following tools: Visual Studio 2022 (https://visualstudio.microsoft.com/thank-you-downloading-visual-studio/?sku=Community&rel=16) Windows Driver Kit (https://docs.microsoft.com/en-us/windows-hardware/drivers/download-the-wdk) Clone the repository and build the driver. Driver Testing To test it in your testing environment run those commands with elevated cmd: bcdedit /set testsigning on After rebooting, create a service and run the driver: sc create nidhogg type= kernel binPath= C:\Path\To\Driver\Nidhogg.sys
sc start nidhogg Debugging To debug the driver in your testing environment run this command with elevated cmd and reboot your computer: bcdedit /debug on After the reboot, you can see the debugging (https://www.kitploit.com/search/label/Debugging) messages in tools such as DebugView (https://learn.microsoft.com/en-us/sysinternals/downloads/debugview). Resources Windows Kernel Programming Book (https://github.com/zodiacon/windowskernelprogrammingbook) Kernel Structure Documentation (https://www.vergiliusproject.com/) Registry Keys Hiding (https://github.com/JKornev/hidden) Process Signatures (https://github.com/itm4n/PPLcontrol) NtCreateThreadEx Hotfix (https://github.com/DarthTon/Blackbone) Contributions Thanks a lot to those people that contributed to this project: BlackOfWorld (https://github.com/BlackOfWorld)

Download Nidhogg (https://github.com/Idov31/Nidhogg)

Dark Reading: Attacks/Breaches
Focus Security Efforts on Choke Points, Not Visibility

By finding the places where attack paths converge, you can slash multiple exposures in one fix for more efficient remediation.

Dark Reading: Attacks/Breaches
Salesforce 'Ghost Sites' Expose Sensitive Corporate Data

Some companies have moved on from using Salesforce. But without remembering to fully deactivate their clouds, Salesforce won't move on from them.

hacking: security in practice
Daxin Backdoor: In-Depth Analysis, Part One

https://external-preview.redd.it/AYPHDLrF2aXqvA7xhx1oWXcNM2MNQNW874XuPtYWUSs.jpg?width=640&crop=smart&auto=webp&s=417196d193a6b24e3acd92092496aa96fb5fc6aa submitted by /u/CodePerfect
[link] [comments]

https://b.thumbs.redditmedia.com/AWrl2k8Z-X4w-p8lDOUOtr5Q6YXnQdXCEqwbdAwSEXE.jpg
* Running Kali on a Raspberry Pi 4b
* Target network is 2.4 GHz provided by a Netgear RAX10 using WPA2-Personal
* Target computer is a Windows box connecting to the router via an ASUS USB-AX56 Nano

I can capture handshakes when I turn the target computer's WiFi off and then on again, so my capturing procedure isn't at fault. However, I have not been able to forcibly deauthenticate the target computer via aireplay-ng or mdk4.

sudo aireplay-ng --deauth 0 -a <router-c <victimwlan0mongives me a string of attempts marked with [ 0| 0 ACKs]sudo mdk4 wlan0mon d -B <router-S <victim just hangs with no output until I hit Ctrl+Csudo mdk4 wlan0mon d -S <victim similarly hangs with no outputsudo mdk4 wlan0mon d -B <router spams the screen with deauth messages but none of them include the MAC of the victim

Also of note - both aireplay-ng and MDK claim to be deauthing my C&C box but no handshakes are captured and the connection isn't broken.I don't **think** I'm doing anything wrong, but I'm not getting the results I expect.Is my router just too resilient, or is there something else I should be adding to my attacks to make them more successful?

edit screencap from the router spec sheet. Looks like I'm playing on hard mode when I should be on easy?

https://preview.redd.it/8jxeltcgn73b1.png?width=351&format=png&auto=webp&s=83da51757f15755a405eb27d763ce504693c8cc4

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

hacking: security in practice
Hacking my “smart” toothbrush

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

Bug Bounty
https://blog.snoopbees.com/bug-bounty-6b6c9844d7cb?source=rss------bug_bounty-5

วันนี้จะมาพูดถึง Bug bounty ว่าคืออะไร พร้อมกับแพลตฟอร์มที่รวบรวมโปรแกรมที่เข้าร่วมโครงการ bug bounty…Continue reading on SnoopBees » (https://blog.snoopbees.com/bug-bounty-6b6c9844d7cb?source=rss------bug_bounty-5)

KitPloit - PenTest Tools!
Nidhogg - All-In-One Simple To Use Rootkit For Red Teams

https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgmwfzqv240jkIhisXrMbsgm3j-ZmNFEnX7G0zfGP5js53wx378tC36F4x0xgcSjBL4wHo6vQR2Pgey2G3qpQQ3gbTHEO1s_LoIkVzoqrFaAUKhyKYeVwLOTd7niZa7_RzABW76Zdeb45e_9tmZofZBl-Jp1-HKaFlJPVz5eOwrhm6gR61IOUIy_EkR4w/w640-h426/h128.png Nidhogg is a multi-functional rootkit for red teams. The goal of Nidhogg is to provide an all-in-one and easy-to-use rootkit with multiple helpful functionalities for red team engagements that can be integrated with your C2 framework via a single header file with simple usage, you can see an example here.

Nidhogg can work on any version of x64 Windows 10 and Windows 11.

This repository contains a kernel driver with a C++ header to communicate with it. Current Features* Process hiding and unhiding
* Process elevation
* Process protection (anti-kill and dumping)
* Bypass pe-sieve
* Thread hiding
* Thread protection (anti-kill)
* File protection (anti-deletion and overwriting)
* File hiding
* Registry keys and values protection (anti-deletion and overwriting)
* Registry keys and values hiding
* Querying currently protected processes, threads, files, registry keys and values
* Arbitrary kernel R/W
* Function patching
* Built-in AMSI bypass
* Built-in ETW patch
* Process signature (PP/PPL) modification
* Can be reflectively loaded
* Shellcode Injection
* APC
* NtCreateThreadEx

* DLL Injection
* APC
* NtCreateThreadEx

* Querying kernel callbacks
* ObCallbacks
* Process and thread creation routines
* Image loading routines
* Registry callbacks

* Removing and restoring kernel callbacks
* ETWTI tampering Reflective loadingSince version v0.3, Nidhogg can be reflectively loaded with kdmapper but because PatchGuard will be automatically triggered if the driver registers callbacks, Nidhogg will not register any callback. Meaning, that if you are loading the driver reflectively these features will be disabled by default:

* Process protection
* Thread protection
* Registry operations PatchGuard triggering featuresThese are the features known to me that will trigger PatchGuard, you can still use them at your own risk.

* Process hiding
* File protecting Basic UsageIt has a very simple usage, just include the header and get started! #include "Nidhogg.hpp"

int main() {
HANDLE hNidhogg = CreateFile(DRIVER_NAME, GENERIC_WRITE | GENERIC_READ, 0, nullptr, OPEN_EXISTING, 0, nullptr);
// ...
DWORD result = Nidhogg::ProcessUtils::NidhoggProcessProtect(pids);
// ...
}SetupBuilding the clientTo compile the client, you will need to install CMake and Visual Studio 2022 installed and then just run: cd <nidhogg\Example
mkdir build
cd build
cmake ..
cmake --build .Building the driverTo compile the project, you will need the following tools:

* Visual Studio 2022
* Windows Driver Kit

Clone the repository and build the driver. Driver TestingTo test it in your testing environment run those commands with elevated cmd: bcdedit /set testsigning onAfter rebooting, create a service and run the driver: sc create nidhogg type= kernel binPath= C:\Path\To\Driver\Nidhogg.sys
sc start nidhoggDebuggingTo debug the driver in your testing environment run this command with elevated cmd and reboot your computer: bcdedit /debug onAfter the reboot, you can see the debugging messages in tools such as DebugView. Resources* Windows Kernel Programming Book
* Kernel Structure Documentation
* Registry Keys Hiding
* Process Signatures
* NtCreateThreadEx Hotfix ContributionsThanks a lot to those people that contributed to this project:

* BlackOfWorld Download Nidhogg