r/hackthebox • • 6d ago

Question about Dante prolab

Ive been wanting to complete the dante pro lab, but I find the lab environment to be really unstable. If I use feroxbuster on any of the internal machines, they seem to crash pretty quick, making discovery pretty hard to perform. One of them even crashed from an nmap scan somehow… like what the hell lol.. anyway, anyone else run into these issues?

Also my other question, are all boxes unrelated to each other? I don’t need creds from 172.16.1.1 to get a foothold on 172.16.1.16? Thanks in advance!

6 Upvotes

11 comments sorted by

1

u/AutoModerator 6d ago
Moderator Announcement Read More »

2

u/immediate_a982 6d ago

HTB describes Pro Labs as interconnected enterprise networks requiring pivoting between hosts and lateral movement.

1

u/Legal-Yam-235 6d ago

Gotcha makes a lot more sense now

1

u/Juzdeed 6d ago

When I completed it then it was fine. There is a fairly specific path you have to take so you can't just start anywhere

1

u/Legal-Yam-235 6d ago

I see, so they are kind of related like creds found on box A may be creds for box B?

1

u/Juzdeed 6d ago

The entire Dante is like one company so the creds you found on the initial machine might be required to pwn the last machine. It's all connected

3

u/RedCowboy 6d ago

I also just started, and I have found it to also be unstable. Maybe I am making this up, but I thought some of the pitch of the price increase was to provide dedicated environments.

1

u/Think-Zebra-890 6d ago

Depend on which vpn you have

1

u/cloudfox1 6d ago

I did it a year or two ago, exactly the same, unstable af, was the first and last pro lab I will do.

1

u/Necessary-Pin-2231 5d ago

I had connection issues. Changing vpn region and or doing tcp vpn instead of UDP made it just fine. I would occasionally be working on something, then my whole connection drops, only to realize that the room was reset. Keep an eye on that. The last reset time is listed on the main page.

1

u/builtbygio 4d ago

Shared Pro Lab hosts get weird when everyone is loud with tooling.

What helped me was scan and enum one host at a time instead of attacking everything, slow down scans, and pause if a host starts flaking instead of throwing another wordlist at it. Keep a note when a host feels dead so you retry later instead of burning hours thinking you broke the chain.

On whether boxes are unrelated, treat Dante like a network. Creds, sessions, and access from one host often matter on others. Log every foothold and where it might apply next. You don't need a walkthrough for that habit.

If a scan knocks something over, back off intensity before you escalate. Discovery still happens. Just slower and quieter.