Hacking Articles Tips Tricks Videos Tutorials
471 subscribers
65.9K 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
Demystifying an XSS payload!

Just found an weird and cool trick by Gareth Heyes, so thought to reverse engineer it and find out the root cause :)Continue reading on Medium »
Read more...
XXE in Public Transport Ticketing Mobile APP

This finding was an another private bug bounty program. The scope of the target was a ticketing android app (Prod). This app was a major…Continue reading on Medium »
Read more...
Deep Web
Russian Game Show.

Hello. I found this hunger games like game show on a youtube video about the dark web. Does anyone know how to access the site? Im very curious and shocked and wanted to take a look at it myself but cant find the onion link anywhere

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

___________________________
@hacking_Attack
@Hacking_Video
Sniffle is a sniffer for Bluetooth 5 and 4.x (LE) using TI CC1352/CC26x2 hardware. Sniffle has a number of useful features, including: Support for BT5/4.2 extended length advertisement and data packets Support for BT5 Channel Selection Algorithms #1 and #2 Support for all BT5 PHY modes (regular 1M, 2M, and coded modes) Support for sniffing only advertisements (https://www.kitploit.com/search/label/Advertisements) and ignoring connections Support for channel map, connection parameter, and PHY change operations Support for advertisement filtering by MAC address and RSSI Support for BT5 extended advertising (non-periodic) Support for capturing advertisements from a target MAC on all three primary advertising channels using a single sniffer. This makes connection detection nearly 3x more reliable than most other sniffers that only sniff one advertising channel. Easy to extend host-side software written in Python PCAP export compatible with the Ubertooth
Prerequisites
TI CC26x2R Launchpad Board: https://www.ti.com/tool/LAUNCHXL-CC26X2R1 or TI CC2652RB Launchpad Board: https://www.ti.com/tool/LP-CC2652RB or TI CC1352R Launchpad Board: https://www.ti.com/tool/LAUNCHXL-CC1352R1 or TI CC1352P1 Launchpad Board: https://www.ti.com/tool/LAUNCHXL-CC1352P GNU ARM Embedded Toolchain: https://developer.arm.com/open-source/gnu-toolchain/gnu-rm/downloads TI CC26x2 SDK 5.10.00.48: https://www.ti.com/tool/download/SIMPLELINK-CC13X2-26X2-SDK TI DSLite Programmer Software: see below Python 3.5+ with PySerial installed If you don't want to go through the effort of setting up a build environment for the firmware, you can just flash prebuilt firmware binaries using UniFlash/DSLite. Prebuilt firmware binaries are attached to releases on the GitHub releases tab of this project. When using prebuilt firmware, be sure to use the Python code corresponding to the release tag rather than master to avoid compatibility issues with firmware that is behind the master branch. Note: it should be possible to compile Sniffle to run on CC1352P Launchpad boards with minimal modifications, but I have not yet tried this.
Installing GCC
The arm-none-eabi-gcc provided through various Linux distributions' package manager often lacks some header files or requires some changes to linker configuration. For minimal hassle, I suggest using the ARM GCC linked above. You can just download and extract the prebuilt executables.
Installing the TI SDK
The TI SDK is provided as an executable binary that extracts a bunch of source code once you accept the license agreement. On Linux and Mac, the default installation directory is inside~/ti/. This works fine and my makefiles expect this path, so I suggest just going with the default here. The same applies for the TI SysConfig tool. Once the SDK has been extracted, you will need to edit one makefile to match your build environment. Within ~/ti/simplelink_cc13x2_26x2_sdk_5_10_00_48 (or wherever the SDK was installed) there is a makefile named imports.mak. The only paths that need to be set here to build Sniffle are for GCC, XDC, and SysConfig. We don't need the CCS compiler. See the diff below as an example, and adapt for wherever you installed things. diff --git a/imports.mak b/imports.mak
index d815a4e94..731d49419 100644
--- a/imports.mak
+++ b/imports.mak
@@ -18,14 +18,14 @@
# will build using each non-empty *_ARMCOMPILER cgtool.
#

-XDC_INSTALL_DIR ?= /home/username/ti/xdctools_3_62_00_08_core
-SYSCONFIG_TOOL ?= /home/username/ti/ccs1030/ccs/utils/sysconfig_1.8.0/sysconfig_cli.sh
+XDC_INSTALL_DIR ?= $(HOME)/ti/xdctools_3_62_00_08_core
+SYSCONFIG_TOOL ?= $(HOME)/ti/sysconfig_1.8.0/sysconfig_cli.sh

FREERTOS_INSTALL_DIR ?= /home/username/FreeRTOSv10.2.1

CCS_ARMCOMPILER ?= /home/username/ti/ccs1030/ccs/tools/compiler/ti-cgt-arm_20.2.4.LTS
TICLANG_ARMCOMPILER ?= /home/username/ti/ccs1030/ccs/tools/compiler/1.2.1.STS

___________________________
@hacking_Attack
@Hacking_Video