Hacking Articles Tips Tricks Videos Tutorials
468 subscribers
65.8K photos
15 videos
157 files
132K links
Exploit
Pentesting
Hacking
Red Team
Blue Team
Kali Linux
Bug Bounty
Black Hat
Cyber security etc

@Hacking_Video
@Hacking_attack
Download Telegram
HOW TO USE STACER TO CLEAN UP YOUR LINUX

If you use linux you might miss ccleaner and it's utilities to clean windows. Well we have different tools on Linux which are free to use.

1️⃣ Install Stacer

For debian and ubuntu users you can install stacer by command-line interface:

sudo apt install software-properties-common

sudo add-apt-repository ppa:oguzhaninan/stacer

[HIT ENTER]

sudo apt update 

sudo apt install stacer

It may happen that you get error messages about the GPG key. You can remove the repository by typing :

sudo add-apt-repository --remove ppa:oguzhaninan/stacer 

If you don't want add repository you can simply download & install the debian package from their github page :
https://github.com/oguzhaninan/Stacer/releases


sudo apt install curl systemd

cd /tmp

wget https://github.com/oguzhaninan/Stacer/releases/download/v1.1.0/stacer_1.1.0_amd64.deb

sudo apt install ./stacer_1.1.0_amd64.deb -y

2️⃣ Start Stacer

sudo stacer

(To run stacer as superuser)

The first tab that you will see is the dashboard with CPU, Memory and Disk.

Screenshot :
https://i.imgur.com/NVekJn1.png

3️⃣ Overview

As far as we can see there are different icons with different features.

Startup ApplicationsShows you all applications which will be launched on startup

System Cleaner Will clean your system of package caches, crash reports, application logs, application caches and t he trash

SearchIs a browsing tool for your file system to find files.(Need to select directory)

Services Shows you all running and not running services.

ProcessesGives an overview about all running processes.

Uninstaller Uninstall packages by search options or manually search.

RessourcesShows CPU, Disk Read Write, Memory, Network, File System (A better taskmanager of windows).

HelpersPrint Hosts.

APT Repository ManagerHere you can manage your Repositories (enable / disable).

SettingsLanguage, Disks, Start Page.

4️⃣ Clean Up

Head over to the »System Cleaner« tab and click "Select all" and click »Search«

Screenshot :
https://i.imgur.com/7uhK9hH.png

Again click »Select all« and then click the 🧹 icon.

Screenshot :
https://i.imgur.com/0oSQ9od.png

Finally your system has been cleared for the first.

Later an advanced tutorial about bleachbit.

Written by @MrBlackX 😘
HOW TO USE SWEEPER TO CLEAN YOUR BROWSER HISTORY

#clean_traces
#privacy
#linux

As you can read, sweeper just clear your browsers like cookies, history, cache etc.

1️⃣ Installation

sudo apt install sweeper

2️⃣ Start Sweeper

sweeper / sudo sweeper

3️⃣ Overview

If you opened sweeper successfully then you can see a tab of "Privacy Settings", here you can choose what you want to clear. Generally you should select all checkboxes.

Screenshot :
https://i.imgur.com/bCZNDYZ.png

The "Settings" button between "File" and "Help" is for the language settings.

You can quit the tool by : ctrl+q

4️⃣ Clean

To clean, we hit the button "Select All", then we click "Clean Up". A warning pop-up will as us if we are sure to delete all data. Just click "Continue"

Screenshot :
https://i.imgur.com/XSrobmV.png

Finally the other box will give you messages what the tool does. The last message will be "Clean up finished".

Screenshot :
https://i.imgur.com/DFyKwVr.png

Written by @MrBlackX 😘
HOW TO USE BLEACHBIT TO CLEAN UP YOUR LINUX

#clean_traces
#privacy
#linux

Today i want to show you how to clean linux with bleachbit.

✍️ Note : For bleachbit you can choose between bleachbit and bleachbit root.

1️⃣ Install Bleachbit

sudo apt install bleachbit

2️⃣ Start Bleachtbit

To start bleachbit, you can either choose the terminal or search start method.

Terminal :

bleachbit # as default user
sudo bleachbit # as root

Search :

Just search "bleachbit" and start either as root or default user.

3️⃣ Overview

If you start Bleachbit first time you will see a preferences pop-up, you can choose my settings.

Screenshot :
https://i.imgur.com/Nn849UW.png

it could happen that you get this error

Screenshot :
https://i.imgur.com/upTAVxB.png

Follow the images and click on the preferences and disable update.

To select items you can for example select "Adobe Reader" to select the items of the "Adobe Reader" automatically.

Screenshot :
https://i.imgur.com/AVqAorZ.png

4️⃣ Cleaning

To clean your computer you click on "Preview" and then on "Clean":

Preview:

Screenshot :
https://i.imgur.com/pEN1yTf.png

Clean(Make you confirmed it):

Screenshot :
https://i.imgur.com/Ehc4vHw.png

Written by @MrBlackX 😘
Hi Folks, hope you are well. As you know developers and pentesters are always into a cat and mouse game. No matter how much we want to…Continue reading on Medium » (https://medium.com/@jaimin_gohel/how-to-bypass-encryption-mechanism-in-android-apps-720e9431bc67?source=rss------bug_bounty-5)
How to bypass encryption mechanism in Android apps

Hi Folks, hope you are well. As you know developers and pentesters are always into a cat and mouse game. No matter how much we want to…Continue reading on Medium »
Read more...
Hacking Articles Tips Tricks Videos Tutorials
Photo
hacking: security in practice
SMB Enumeration Guide

Server Message Block is a network protocol used to provide shared access to files, printers, and serial ports between nodes on a network. SMB servers can be accessed through various command-line tools such as SMBClient or through file browsing tools. This service runs on either port 139 or port 445 by default.

https://steflan-security.com/smb-enumeration-guide/

submitted by /u/cantchooseone96
[link] [comments]
Android-PIN-Bruteforce - Unlock An Android Phone (Or Device) By Bruteforcing The Lockscreen PIN
http://www.kitploit.com/2021/04/android-pin-bruteforce-unlock-android.html
Unlock an Android phone (or device) by bruteforcing (https://www.kitploit.com/search/label/Bruteforcing) the lockscreen PIN. Turn your Kali Nethunter phone into a bruteforce PIN cracker for Android devices! How it works
It uses a USB OTG cable to connect the locked phone to the Nethunter device. It emulates a keyboard, automatically tries PINs, and waits after trying too many wrong guesses. [Nethunter phone] <--> [USB cable] <--> [USB OTG adaptor] <--> [Locked Android phone] The USB HID Gadget driver provides emulation of USB Human Interface Devices (HID). This enables an Android Nethunter device to emulate keyboard input to the locked phone. It's just like plugging a keyboard into the locked phone and pressing keys. This takes just over 16.6 hours with a Samsung S5 to try all possible 4 digit PINs, but with the optimised PIN list it should take you much less time.
You will need
A locked Android phone A Nethunter phone (or any rooted Android with HID kernel support) USB OTG (On The Go) cable/adapter (USB male Micro-B to female USB A), and a standard charging cable (USB male Micro-B to male A). That's all!
Benefits
Turn your NetHunter phone into an Android PIN cracking machine Unlike other methods, you do not need ADB or USB debugging enabled on the locked phone The locked Android phone does not need to be rooted You don't need to buy special hardware, e.g. Rubber Ducky, Teensy, Cellebrite, XPIN Clip, etc. You can easily modify the backoff time to crack other types of devices It works!
Features
Crack PINs of any length from 1 to 10 digits Use config files to support different phones Optimised PIN lists for 3,4,5, and 6 digit PINs Bypasses phone pop-ups including the Low Power warning Detects when the phone is unplugged or powered off, and waits while retrying every 5 seconds Configurable delays of N seconds after every X PIN attempts Log file
Installation
TBC
Executing the script
If you installed the script to /sdcard/, you can execute it with the following command. bash ./android-pin-bruteforce Note that Android mounts /sdcard with the noexec flag. You can verify this with mount.
Usage

Android-PIN-Bruteforce (0.1) is used to unlock an Android phone (or device) by bruteforcing the lockscreen PIN.
Find more information at: https://github.com/urbanadventurer/Android-PIN-Bruteforce

Commands:
crack Begin cracking PINs
resume Resume from a chosen PIN
rewind Crack PINs in reverse from a chosen PIN
diag Display diagnostic information
version Display version information and exit

Options:
-f, --from PIN Resume from this PIN
-a, --attempts Starting from NUM incorrect attempts
-m, --mask REGEX Use a mask for known digits in the PIN
-t, --type TYPE Select PIN or PATTERN cracking
-l, --length NUM Crack PINs of NUM length
-c, --config FILE Specify configuration file to load
-p, --pinlist FILE Specify a custom PIN list
-d, --dry-run Dry run for testing. Does n't send any keys.
-v, --verbose Output verbose logs

Usage:
android-pin-bruteforce [options]

Supported Android Phones/Devices
This has been successfully tested with various phones including the Samsung S5, S7, Motorola G4 Plus and G5 Plus. It can unlock Android versions 6.0.1 through to 10.0. The ability to perform a bruteforce attack doesn't depend on the Android version in use. It depends on how the device vendor developed their own lockscreen. Check the Phone Database for more details https://github.com/urbanadventurer/Android-PIN-Bruteforce/wiki/Phone-Database
PIN Lists
Optimised PIN lists are used by default unless the user selects a custom PIN list.
Cracking PINs of different lengths
Use the --length commandline option. Use this command to crack a 3 digit PIN, ./android-pin-bruteforce crack --length 3 Use this command to crack a 6 digit PIN ./android-pin-bruteforce crack --length 6
Where did the optimised PIN lists come from?
The optimised PIN lists were generated by extracting numeric passwords from database leaks then sorting by frequency. All PINs that did not appear in the password leaks were appended to the list. The optimised PIN lists were generated from Ga$$Pacc DB Leak (21GB decompressed, 688M Accounts, 243 Databases, 138920 numeric passwords).
The 4 digit PIN list
The reason that the 4 digit PIN list is used from a different source is because it gives better results than the generated list from Ga$$Pacc DB Leak. optimised-pin-length-4.txt is an optimised list of all possible 4 digit PINs, sorted by order of likelihood. It can be found with the filename pinlist.txt at https://github.com/mandatoryprogrammer/droidbrute This list is used with permission from Justin Engler & Paul Vines from Senior Security Engineer, iSEC Partners, and was used in their Defcon talk, Electromechanical PIN Cracking with Robotic Reconfigurable Button Basher (and C3BO) (https://www.defcon.org/html/defcon-21/dc-21-speakers.html#Engler)
Cracking with Masks
Masks use regular expressions (https://www.kitploit.com/search/label/Regular%20Expressions) with the standard grep extended format. ./android-pin-bruteforce crack --mask "...[45]" --dry-run To try all years from 1900 to 1999, use a mask of 19.. To try PINs that have a 1 in the first digit, and a 1 in the last digit, use a mask of 1..1 To try PINs that end in 4 or 5, use ...[45]
Configuration for different phones
Device manufacturers create their own lock screens that are different to the default or stock Android. To find out what keys your phone needs, plug a keyboard into the phone and try out different combinations. Load a different configuration file, with the --config FILE commandline parameter. Example: ./android-pin-bruteforce --config ./config.samsung.s5 crack You can also edit the config file by customising the timing and keys sent. The following configuration variables can be used to support a different phone's lockscreen. # Timing
## DELAY_BETWEEN_KEYS is the period of time in seconds to wait after each key is sent
DELAY_BETWEEN_KEYS=0.25

## The PROGRESSIVE_COOLDOWN_ARRAY variables act as multi-dimensional array to customise the progressive cooldown
## PROGRESSIVE_ARRAY_ATTEMPT_COUNT__________ is the attempt number
## PROGRESSIVE_ARRAY_ATTEMPTS_UNTIL_COOLDOWN is how many attempts to try before cooling down
## PROGRESSIVE_ARRAY_COOLDOWN_IN_SECONDS____ is the cooldown in seconds

PROGRESSIVE_ARRAY_ATTEMPT_COUNT__________=(1 11 41)
PROGRESSIVE_ARRAY_ATTEMPTS_UNTIL_COOLDOWN=(5 1 1)
PROGRESSIVE_ARRAY_COOLDOWN_IN_SECONDS____=(30 30 60)

## SEND_KEYS_DISMISS_POPUPS_N_SECONDS_BEFORE_COOLDOWN_END defines how many seconds before the end of the cooldown period, keys will be sent
# set to 0 to disable
SEND_KEYS_DISMISS_POPUPS_N_SECONDS_BEFORE_COOLDOWN_END=5
## SEND_KEYS_DISMISS_POPUPS_AT_COOLDOWN_END configures the keys that are sent to dismiss messages and popups before the end of the cooldown period
SEND_KEYS_DISMISS_POPUPS_AT_COOLDOWN_END="enter enter enter"

## KEYS_BEFORE_EACH_PIN configures the keys that are sent to prompt the lock screen to appear. This is sent before each PIN.
## By default it sends "escape enter", but some phones will respond to other keys.

# Examples:
# KEYS_BEFORE_EACH_PIN="ctrl_escape enter"
# KEYS_BEFORE_EACH_PIN="escape space"
KEYS_BEFORE_EACH_PIN="escape enter"

## KEYS_STAY_AWAKE_DURING_COOLDOWN the keys that are sent during the cooldown period to keep the phone awake
KEYS_STAY_AWAKE_DURING_COOLDOWN="enter"

## SEND_KEYS_STAY_AWAKE_DURING_COOLDOWN_EVERY_N_SECONDS how often the keys are sent, in seconds
SEND_KEYS_STAY_AWAKE_DURING_COOLDOWN_EVERY_N_SECONDS=5

## DELAY_BEFORE_STARTING is the period of time in seconds to wait before the bruteforce begins
DELAY_BEFORE_STARTING=2
## KEYS_BEFORE_STARTING config ures the keys that are sent before the bruteforce begins
KEYS_BEFORE_STARTING="enter"

Popups
We send keys before the end of the cooldown period, or optionally during the cooldown period. This is to keep the lockscreen app active and to dismiss any popups about the number of incorrect PIN attempts or a low battery warning.
Test sending keys from the NetHunter phone

Test sending keys from the terminal
Use ssh from your laptop to the NetHunter phone, and use this command to test sending keys: In this example, the enter key is sent. echo "enter" | /system/xbin/hid-keyboard /dev/hidg0 keyboard In this example, ctrl-escape is sent. echo "left-ctrl escape" | /system/xbin/hid-keyboard /dev/hidg0 keyboard Note: Sending combinations of keys in config file variables is different. Currently only ctrl_escape is supported. In this example, keys a, b, c are sent. echo a b c | /system/xbin/hid-keyboard /dev/hidg0 keyboard
Test sending keys from an app
This Android app is a virtual USB Keyboard that you can use to test sending keys. https://store.nethunter.com/en/packages/remote.hid.keyboard.client/
How to send special keys
Use this list for the following variables: KEYS_BEFORE_EACH_PIN KEYS_STAY_AWAKE_DURING_COOLDOWN KEYS_BEFORE_STARTING To send special keys use the following labels. This list can be found in the hid_gadget_test source code. Key label Key label left-ctrl f6 right-ctrl f7 left-shift f8 right-shift f9 left-alt f10 right-alt f11 left-meta f12 right-meta insert return home esc pageup bckspc del tab end spacebar pagedown caps-lock right f1 left f2 down f3 kp-enter f4 up f5 num-lock To send more than one key at the same time, use the following list: ctrl_escape (This sends left-ctrl and escape) If you need more key combinations please open a new issue in the GitHub issues list.
Customising the Progressive Cooldown
The following section of the config file controls the progressive cooldown. ## The PROGRESSIVE_COOLDOWN_ARRAY variables act as multi-dimensional array to customise the progressive cooldown
## PROGRESSIVE_ARRAY_ATTEMPT_COUNT__________ is the attempt number
## PROGRESSIVE_ARRAY_ATTEMPTS_UNTIL_COOLDOWN is how many attempts to try before cooling down
## PROGRESSIVE_ARRAY_COOLDOWN_IN_SECONDS____ is the cooldown in seconds

PROGRESSIVE_ARRAY_ATTEMPT_COUNT__________=(1 11 41)
PROGRESSIVE_ARRAY_ATTEMPTS_UNTIL_COOLDOWN=(5 1 1)
PROGRESSIVE_ARRAY_COOLDOWN_IN_SECONDS____=(30 30 60)

The array is the same as this table. attempt number attempts until cooldown cooldown 1 5 30 11 1 30 41 1 60
Why can't you use a laptop?
This works from an Android phone because the USB ports are not bidirectional, unlike the ports on a laptop.
How Android emulates a keyboard
Keys are sent using /system/xbin/hid-keyboard. To test this and send the key 1 you can use echo 1 | /system/xbin/hid-keyboard dev/hidg0 keyboard In Kali Nethunter, /system/xbin/hid-keyboard is a compiled copy of hid_gadget_test.c. This is a small program for testing the HID gadget driver that is included in the Linux Kernel. The source code for this file can be found at https://www.kernel.org/doc/html/latest/usb/gadget_hid.html and https://github.com/aagallag/hid_gadget_test.
 Troubleshooting

If it is not bruteforcing PINs

Check the orientation of the cables
The Nethunter phone should have a regular USB cable attached, while the locked phone should have an OTG adaptor attached. The OTG cable should be connected to the locked Android phone. The regular USB cable should be connected to the Nethunter phone. Refer to the graphic on how to connect the phones.
Check it is emulating a keyboard
You can verify that the NetHunter phone is succesfully emulating a keyboard by connecting it to a computer using a regular charging/data USB cable. Open a text editor like Notepad while it is cracking and you should see it entering PIN numbers into the text editor. Note that you will not need an OTG cable for this.
Try restarting the phones
Try powering off the phones and even taking out the batteries if that is possible.
Try new cables
Try using new cables/adaptors as you may have a faulty cable/adaptor.
If it doesn't unlock the phone with a correct PIN
You might be sending keys too fast for the phone to process. Increase the DELAY_BETWEEN_KEYS variable in the config file.  If you don't see 4 dots come up on the phone's screen then maybe it is not receiving 4 keys.
 Managing Power Consumption
If your phone runs out of power too soon, follow these steps: Make sure both phones are fully charged to 100% before you begin Reduce the screen brightness on both the victim phone and NetHunter phone if possible Place both phones into Airplane mode, however you may want to enable WiFi to access the NetHunter phone via SSH. The locked phone will power the NetHunter phone, because it appears as a keyboard accessory Use a USB OTG cable with a Y splitter for an external power supply, to allow charging of the NetHunter phone while cracking Take breaks to charge your devices. Pause the script with CTRL-Z and resume with the fg shell command. Avoid the SEND_KEYS_STAY_AWAKE_DURING_COOLDOWN_EVERY_N_SECONDS configuration option. This will cause the locked phone to use more battery to keep the screen powered. Instead use the SEND_KEYS_DISMISS_POPUPS_N_SECONDS_BEFORE_COOLDOWN_END option (Default).
Check the Diagnostics Report
Use the command diag display diagnostic information. bash ./android-pin-bruteforce diag If you receive this message when the USB cable is plugged in then try taking the battery out of the locked Android phone and power cycling it. [FAIL] HID USB device not ready. Return code from /system/xbin/hid-keyboard was 5.
How the usb-devices command works
The diagnostics command uses the usb-devices script but it is only necessary as part of determining whether the USB cables are incorrectly connected. This can be downloaded from https://github.com/gregkh/usbutils/blob/master/usb-devices
Use verbose output
Use the --verbose option to check the configuration is as expected. This is especially useful when you are modifying the configuration.
Use the dry-run
Use the --dry-run option to check how it operates without sending any keys to a device. This is especially useful when you are modifying the configuration or during development. Dry run will: Not send any keys Will continue instead of aborting if the KEYBOARD_DEVICE or HID_KEYBOARD is missing.
HID USB Mode
Try this command in a shell on the NetHunter phone: /system/bin/setprop sys.usb.config hid
 Known Issues
This cannot detect when the correct PIN is guessed and the phone unlocks. Your phones may run out of  battery before the correct PIN is found. Don't trust phone configuration files from unknown sources without reviewing them first. The configuration files are shell scripts and could include malicious commands.
 Roadmap
[DONE] Works [DONE] Detects USB HID failures [DONE] Improve Usage and commandline options/config files [DONE] Add bruteforce for n digit PINs [DONE] Mask for known digits [DONE] Crack PIN list in reverse (to find which recent PIN unlocked the device) [DONE] Implement configurable lockscreen prompt [DONE] Implement cooldown change after 10 attempts [WORKING] Find/test more devices to bruteforce Add progress bar Add ETA ASCII art Nicer GUI for NetHunter Implement for iPhone Detect when a phone is unlocked (Use Nethunter camera as a sensor?) Crack Android Patterns (try common patterns first)
 Contributing
Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change. Please make sure to update tests as appropriate.
 Authors and acknowledgment
Developed by Andrew Horton (@urbanadventurer).  The following people have been very helpful: Vlad Filatov (@v1adf): Testing many phones for the Wiki Phone Database
Motivation