notes linux · hard · 40 pts · 2026-06-20 2026-08-07 · 2 min read · updated 2026-09-20

Hack The Box Nimbus Stats (Hard Linux)

HTB Nimbus: active hard Linux box, Season 11 week 5. Rated 4.5/5 from 192 reviews, 4,445 user owns. Difficulty read and prep, spoiler-free.

Hack The Box Nimbus Stats (Hard Linux)
os
Linux
difficulty
Hard
points
40 pts
released
2026-06-20

Nimbus is week 5 of Hack The Box Season 11, a hard Linux machine by dotguy and TheCyberGeek, worth 40 points and 1,105 XP. It is still active, so what follows is the season data and an honest read of the difficulty. No chain, no flags.

The numbers

  
Machine ID912
DifficultyHard (40 pts / 1,105 XP)
OSLinux
Released2026-06-20 (week 5)
Makerdotguy, TheCyberGeek
Rating4.5 / 5 from 192 reviews
User owns4,445
Root owns3,649
User → root drop17.9%
User blood7m 8s by Ap4sh
Root blood48m 42s by s30s0ft

Community difficulty votes:

BucketVotesShare
Hard71726.7%
Too Hard38214.2%
Medium37113.8%
Bit Hard35813.3%
Too Easy2439.0%

Total votes: 2,690.

Difficulty read

Nimbus has the most distinctive shape of any released box this season. User blood fell in 7m08s, faster than several of the Easy boxes, and root blood took 48m42s. That 41m34s gap is the widest of any Linux box in Season 11.

The user-to-root drop backs it up at 17.9%, second only to Connected. Nearly one in five people who got in never got root.

So: approachable foothold, punishing privesc. The community votes agree it’s a real Hard, with Hard, Too Hard and Bit Hard taking about 54% of 2,690 votes between them, and they liked it anyway, at 4.5 stars. That’s the best rating of any Linux box this season.

Plan your time accordingly. If you budget the usual split of recon-heavy, privesc-light, you will run out of evening. The foothold is not where this box lives.

What to have ready

  • Assume multiple hops. Map the whole surface before exploiting anything. Hard boxes punish tunnel vision more than they punish slow recon.
  • Have pivoting ready before you need it: chisel or ligolo-ng set up and tested, plus proxychains configured, so an internal service doesn’t stall you for an hour.
  • Expect a custom application. Source review, logic flaws and chained primitives beat scanner output at this tier.
  • Containers and service accounts matter. Check whether your shell is in a container, then look at what it can reach rather than what it can read.
  • Privesc will be a chain rather than a one-liner. Capabilities, writable systemd units, misconfigured group membership and inter-service trust are the usual joints.

When the writeup lands

We publish full chains after a box retires, never while it’s active, and we don’t hand them to anyone outside the team. Nimbus retires at the end of Season 11, and the writeup goes up that week, in the same format as the HTB Mango one.

If you’d rather not wait, the team’s internal notes go out in our Discord first. That’s also where people work through active boxes together, which is the part you’re actually allowed to do while Nimbus is still live.

Retired Linux boxes we’ve already published:

This post is licensed under CC BY 4.0 by the author.