UNDERCODE COMMUNITY
2.67K subscribers
1.23K photos
31 videos
2.65K files
79.5K links
🦑 Undercode Cyber World!
@UndercodeCommunity


1️⃣ World first platform which Collect & Analyzes every New hacking method.
+ AI Pratice
@Undercode_Testing

2️⃣ Cyber & Tech NEWS:
@Undercode_News

3️⃣ CVE @Daily_CVE

Web & Services:
Undercode.help
Download Telegram
Forwarded from Exploiting Crew (Pr1vAt3)
Forwarded from Exploiting Crew (Pr1vAt3)
Forwarded from Exploiting Crew (Pr1vAt3)
Forwarded from Exploiting Crew (Pr1vAt3)
Forwarded from Exploiting Crew (Pr1vAt3)
🦑Python Remote Administration Tool (RAT)

☠️This feature list outlines a Python-based Remote Administration Tool (RAT) with extensive functionality across Windows, macOS, and Linux. Here's a detailed breakdown of the core features and their implications:

>> Cross-Platform Support
- Core Utilities
- Command and file auto-completion: Enhances usability, streamlining interactions.
- Antivirus detection: Useful for evasion tactics or reconnaissance.
- Display monitor control: Provides surveillance or energy management options.
- File/Directory manipulation: Hiding or unhiding files adds stealth capabilities.
- Hosts file modification: Potential for blocking or redirecting network traffic.
- Environment variables access: Useful for reconnaissance and configuration.
- Keylogger: Logs keystrokes with options to manage logs.
- Target machine info: Location and system details provide situational awareness.
- Python script execution: Flexibility for custom tasks.
- Screenshots: Remote visual access to the system's desktop.
- VM detection: Helps evade analysis environments.
- File transfer: Enables exfiltration or delivery of additional payloads.
- Password hash dumping: Attempts to extract sensitive authentication details.
- Payload disguise: Adds stealth by masquerading as legitimate applications.

>> Windows-Specific Features
- Credential Harvesting
- User/password dialog: Captures user input for credentials.
- Chrome password dumping: Extracts stored browser passwords.
- System Control
- Log clearing: Obscures tracks by erasing event logs.
- Service control: Manipulates RDP, UAC, and Windows Defender.
- File timestamp editing: Alters evidence of file access or modification.
- Custom popups: Creates distractions or elicits user input.
- Hardware Interaction
- Webcam snapshots: Spies on users via their webcam.
- Drive info: Provides details about connected drives.
- Registry summary: Fetches system configuration details.

>> macOS-Specific Features
- Credential Harvesting
- Similar password dialog as Windows.
- System Customization
- Changes login text, potentially confusing or misleading users.
- Webcam snapshots: Monitors users like the Windows version.

>> macOS/Linux Features
- SSH pivoting: Leverages the target system to access other hosts.
- Sudo command execution: Elevates privilege level for administrative tasks.
- Bruteforce user password: Exploits weak password practices.
- Webcam snapshots: Unverified functionality on Linux.

>> Transport and Encryption
- AES encryption secures host-target communication, with keys shared manually between systems for authentication.

>> Payload Installation
- NSIS installers (Windows): Packages payloads with elevation utilities.
- Makeself installers (macOS/Linux): Simplifies deployment and persistence.

>> Setup and Dependencies
- The project uses Python 2.7, various libraries like PyCrypto, Requests, and platform-specific tools like PyInstaller, PyObjC, and py2exe.


🦑 Here are the commands for setting up and running Stitch from the specified GitHub repository:

>> Installation Commands
1. For Windows:
   pip install -r win_requirements.txt


2. For macOS:
   pip install -r osx_requirements.txt


3. For Linux:
   pip install -r lnx_requirements.txt

>> Execution Commands
1. Run using Python:
   python main.py

2. Run as an executable (if permissions are set):
   ./main.py


🦑Be Ethical, Use it for learning purposes !!!
@UndercodeCommunity
▁ ▂ ▄ U𝕟𝔻Ⓔ𝐫Ć𝔬𝓓ⓔ ▄ ▂ ▁
Forwarded from Exploiting Crew (Pr1vAt3)
🦑UEFI BIOS Hacking Notes:

I started my Desktop System after a couple of weeks, and found that the ASUS Z170-AR 1.03 motherboard was failing to POST successfully with the following error message:


1️⃣USB Device Over Current Status Detected !!
System Will Shut Down After 15 Seconds.
(November-2020): After downloading the BoardView file for a similar motherboard, I learned about the various OC (over current) detection sub-circuits present on the motherboard. I systematically checked the reference voltages present at all (4) of those voltage dividers and found them to be 3.26+ volts. Note: These voltage dividers ("sensors") are directly connected to the Mobo's PCH.

I also carried out the following debugging steps:

All of the USB ports were providing +5v and were able to detect the keyboard during BIOS POST (Caps Lock responded). They all seemed to be OK.

The single USB-C port on this mobo was also providing power to charge things just fine.

I connected the USB keyboard to the PS2 port but the BIOS was disabling all inputs when this 'USB OC' problem is detected.

All of the USB devices were subsequently disconnected for safety.

The cables for the front-panel USB connectors were disconnected as well.

However, the BIOS error about 'USB OC' persisted. I then dumped the BIOS from the W25Q128FV BIOS chip (thankfully present in DIP-8 form factor) using flashrom on Linux with CH341A Mini USB BIOS Programmer hardware.
Forwarded from Exploiting Crew (Pr1vAt3)
2️⃣
$ sudo ./flashrom --programmer ch341a_spi -r bios_dump_another.rom
flashrom v1.2-136-ged341cf on Linux 5.8.0-26-lowlatency (x86_64)
flashrom is free software, get the source code at https://flashrom.org

Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
Found Winbond flash chip "W25Q128.V" (16384 kB, SPI) on ch341a_spi.
Reading flash... done.
Forwarded from Exploiting Crew (Pr1vAt3)
3️⃣This dumping process took around 2.5 minutes. The dump matched the "BIOS ROM file" which I extracted from the Z170-AR-ASUS-3801.CAP (downloaded from ASUS' website) using UEFITool.

Note: This board uses the ASM1142 USB 3.0 chip which has its own over current (OC) detection. I couldn't find the BoardView for my Z170-AR 1.03 motherboard and hence I had to pause the hardware debugging process at this point.

Next, switching to the SW sides of things, I was able to patch the ASUS BIOS using UEFITool, GHIDRA, Cutter (Rizin GUI), and WinHex to bypass this USB OC error message (and the subsequent PC hang)!

binwalk -eM bios.rom # bios.rom is extracted from UEFItool.

[user@random _flash-me.rom.extracted]$ find . -type f -exec strings {} \; | grep "USB Device"
USB Device Over Current Status Detected !!
Forwarded from Exploiting Crew (Pr1vAt3)
4️⃣I wrote the modded BIOS back using the following command,

$ sudo ./flashrom --programmer ch341a_spi -v 1402_modded_working.rom
flashrom v1.2-169-g10d71d9 on Linux 5.8.0-33-lowlatency (x86_64)
flashrom is free software, get the source code at https://flashrom.org

Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
Found Winbond flash chip "W25Q128.V" (16384 kB, SPI) on ch341a_spi.
Verifying flash... VERIFIED.
...
After patching the BIOS, I was able to boot into the system! After logging in, I was able to confirm that ASM1142 chip is generating those OC (Over Current) signals.

$ sudo dmesg | grep over-cu
[ 1.082715] usb usb4-port2: over-current condition
[ 1.086705] usb usb3-port2: over-current condition
$ lspci
...
00:14.0 USB controller: Intel Corporation 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller (rev 31)
02:00.0 USB controller: ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller
03:00.0 PCI bridge: ASMedia Technology Inc. ASM1083/1085 PCIe to PCI Bridge (rev 04)
This controller can be disabled with the following command.

$ echo -n "0000:02:00.0" | sudo tee /sys/bus/pci/drivers/xhci_hcd/unbind
Here is a Linux hack to ignore the misbehaving ASM1142 USB 3.0 controller on bootup.

$ cat /etc/rc.local
#!/bin/bash

# "Fix" "2:00.0 USB controller: ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller"
echo -n "0000:02:00.0" | sudo tee -a /sys/bus/pci/drivers/xhci_hcd/unbind

exit 0
This made the system pretty usable again. Victory!?

🦑Be Ethical, Use it for learning purposes !!!

Ref: Hacking Notes
@UndercodeCommunity
▁ ▂ ▄ U𝕟𝔻Ⓔ𝐫Ć𝔬𝓓ⓔ ▄ ▂ ▁