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
hacking: security in practice
Linkedin Account Generator

I am writing a script to generate linkedin account for digital makerting , I am in testing phase, so I created various accounts manually with different cellphone sms verification numbers, but days after that without any actions, all these accounts are blocked with restricctions including my original account, I need to upload an real ID document to recovery each of them, Does anybody knows how Microsoft/ Linkedin known these accounts are 'fakes' and how linked with my original account? I am thinking about use diferent proxies to manage my accounts, but I donot know if i am right? And how to bypass this posible detection.

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

___________________________
@hacking_Attack
@Hacking_Video
hacking: security in practice
Private hacking eviroment

Hey guys, how would you aproach creating really private hacking enviroment? I thought about QubesOs hacking but i think it would be kinda painfull, also thought about creating Hacking vm's inside of base Debian Os and wiping them weekly, but yeah i've gotta grab some ideas on how to aproach it with it actually being practical.

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

___________________________
@hacking_Attack
@Hacking_Video
hacking: security in practice
Password database dumps

are there places where password database dumps are available for download? I would love to do some of my own analysis.

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

___________________________
@hacking_Attack
@Hacking_Video
Dark Reading: Attacks/Breaches
Navigating Nobelium: Lessons From Cloud Hopper & NotPetya

Nearly every organization should assume that it is at risk, but there are ways of countering the tactics used by advanced persistent threats.
Dark Reading: Attacks/Breaches
The Looming CISO Mental Health Crisis — and What to Do About It, Part 1

The next big threat to corporate security may not be a new strain of malware or innovative attacker tactics, techniques, and processes. It may be our own mental health.
Mininode - A CLI Tool To Reduce The Attack Surface Of The Node.js Applications By Using Static Analysis

Mininode is a CLI tool to reduce the attack surface of the Node.js applications by using static analysis of source code. It supports two modes of reduction (1) coarse, (2) fine. Mininode constructs the dependency graph (modules and functions used) of the application starting from main file, i.e. entry point of the application. Mininode initializes entry point to package.json file's main field if it exists. Otherwise default to index.js. Example usage: node index.js --mode=(coarse|fine). Below is the list of options that can be passed to Mininode. Options List of command line options that can be passed to mininode. --destination, -d: the path where mininode will save the reduced Node.js application. The default value: mininode. --dry-run: just generates mininode.json without modifying the initial application. --mode, -m: reduction mode. The value can be either coarse or fine. In coarse mode mininode will perform only coarse-grained reduction. While in fine mode mininode will perform fine-grained reduction. In general coarse-grained reduction is more reliable, because mininode will not try to reduce unused functions inside the module. Default value: coarse. --silent: console output is disabled. This will improve the performance of the mininode. --verbose: outputs additional information to the console. The default value: false --log: mininode will generate log file inside, which contains dependency graph of the application in json format. The default value: true. --log-output: the name of the log file generated by mininode. The default value: mininode.json. --compress-log: compresses the final log file. By default it will dump everything into log file. In production it is advised to pass the --compress-log flag to save space. --seeds: seed files from where mininode will start building dependency graph. You can provide many seed files by separating them with colon. --skip-stat: skips calculating the statistics --skip-reduction: if passed mininode will not reduce the JavaScript files. The default value: false. --skip-remove: if passed mininode will not remove unused JavaScript files. The default value: false. Limitaions Mininode uses static analysis, which means it can not reduce the attack surface of the Node.js application which uses dynamic behaviour, such as eval. If Mininode detects dynamic behaviour in the application it exits with error DYNAMIC_BEHAVOUR_DETECTED. Research Paper You can read more about the details of our work in the following research paper: Mininode: Reducing the Attack Surface of Node.js Applications PDF Igibek Koishybayev, Alexandros Kapravelos Proceedings of the International Symposium on Research in Attacks, Intrusions and Defenses (RAID), 2020 If you use Mininode in your research, consider citing our work using this Bibtex entry: @conference{mininode-raid20, title = {{Mininode: Reducing the Attack Surface of Node.js Applications}}, author = {Koishybayev, Igibek and Kapravelos, Alexandros}, booktitle = {{Proceedings of the International Symposium on Research in Attacks, Intrusions and Defenses (RAID)}}, year = {2020}} Download Mininode
Read more...

___________________________
@hacking_Attack
@Hacking_Video
Mininode is a CLI tool to reduce the attack surface of the Node.js applications by using static analysis (https://www.kitploit.com/search/label/Static%20Analysis) of source code. It supports two modes of reduction (1) coarse, (2) fine. Mininode constructs the dependency graph (modules and functions used) of the application starting from main file, i.e. entry point of the application. Mininode initializes entry point to package.json file's main field if it exists. Otherwise default to index.js. Example usage: node index.js --mode=(coarse|fine). Below is the list of options that can be passed to Mininode.
Options List of command line (https://www.kitploit.com/search/label/Command%20Line) options that can be passed to mininode. --destination, -d: the path where mininode will save the reduced Node.js application. The default value: mininode. --dry-run: just generates mininode.json without modifying the initial application. --mode, -m: reduction mode. The value can be either coarse or fine. In coarse mode mininode will perform only coarse-grained reduction. While in fine mode mininode will perform fine-grained reduction. In general coarse-grained reduction is more reliable, because mininode will not try to reduce unused functions inside the module. Default value: coarse. --silent: console output is disabled. This will improve the performance (https://www.kitploit.com/search/label/Performance) of the mininode. --verbose: outputs additional information to the console. The default value: false --log: mininode will generate log file inside, which contains dependency graph of the application in json format. The default value: true. --log-output: the name of the log file generated by mininode. The default value: mininode.json. --compress-log: compresses the final log file. By default it will dump everything into log file. In production it is advised to pass the --compress-log flag to save space. --seeds: seed files from where mininode will start building dependency graph. You can provide many seed files by separating them with colon. --skip-stat: skips calculating the statistics --skip-reduction: if passed mininode will not reduce the JavaScript files. The default value: false. --skip-remove: if passed mininode will not remove unused JavaScript files. The default value: false. Limitaions Mininode uses static analysis, which means it can not reduce the attack surface of the Node.js application which uses dynamic behaviour, such as eval. If Mininode detects dynamic behaviour in the application it exits with error DYNAMIC_BEHAVOUR_DETECTED. Research Paper You can read more about the details of our work in the following research paper: Mininode: Reducing the Attack Surface of Node.js Applications [PDF] (https://kapravelos.com/publications/mininode-raid20.pdf)
Igibek Koishybayev, Alexandros Kapravelos
Proceedings of the International Symposium on Research (https://www.kitploit.com/search/label/Research) in Attacks, Intrusions and Defenses (RAID), 2020 If you use Mininode in your research, consider citing our work using this Bibtex entry: @conference{mininode-raid20,
title = {{Mininode: Reducing the Attack Surface of Node.js Applications}},
author = {Koishybayev, Igibek and Kapravelos, Alexandros},
booktitle = {{Proceedings of the International Symposium on Research in Attacks, Intrusions and Defenses (RAID)}},
year = {2020}
}

Download Mininode (https://github.com/wspr-ncsu/mininode)

___________________________
@hacking_Attack
@Hacking_Video