Shark Jack Display
1.0.0 commercialFree plan: not checked yet
The section your link pointed to isn't on Shark Jack Display's page any more, so we've brought you to the top.
Shark Jack Display by Hak5 is a portable network attack and automation tool for pentesters and systems administrators for wired network auditing.
What you can do now
Summary
Shark Jack Display is a commercial piece of hacking hardware that plugs into wired networks to run automated attack payloads, built by Hak5 as an on-site device rather than software you install, since it's a portable unit carried to the target network and connected directly over Ethernet. It targets pentesters and systems administrators running social engineering engagements and opportunistic wired network audits, and Hak5's documentation describes it as an evolution of the original Shark Jack and Shark Jack Cable, adding a display for on-device feedback during use in the field. Configuration and payload development happen through a Linux shell exposed on the device, alongside internet connectivity and software update support. It launched in 2026, making it Hak5's newest entry in this hardware line rather than an established, long-running project.
Shark Jack Display by Hak5 is a portable network attack and automation tool for pentesters and systems administrators for wired network auditing.
How Shark Jack Display helps
What can I learn about a wired network just by plugging into an open jack?
runs an automated attack payload the moment it connects over Ethernet, so a jack left live in a lobby or conference room hands back results without needing a laptop on site
Did the payload succeed while I was walking away from the drop point?
shows on-device feedback on its own display, so a pentester can confirm the run completed without pulling out another device to check
What happened during a drop I can't sit and watch?
the Linux shell on the device holds the results and logs from the run, reachable afterward to see what the payload did while unattended
How do I tailor an attack to the specific engagement I'm running?
payload development happens directly on the device's exposed Linux shell, so the behavior run against the target network is whatever was written and loaded beforehand
Am I running the latest version of my attack logic on the device?
software update support over its internet connectivity lets the device pull current updates, so a unit carried between engagements can be refreshed rather than relying on whatever shipped on it
Languages
Device
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
Five scores for Shark Jack Display, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail Shark Jack Display puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Website history
hak5.org, every changeHak5's home and pricing pages and 42 more pages as they looked each month from October 2021 to November 2026: 55 renders, 4 changes of tagline or palette. Step through them, play them, or put any two months side by side.
Website history is included with Researcher and Business.
See plans → Already subscribed? Sign in →← → or h l a month · Shift a year · [ ] previous / next change · Space play · 1 2 3 page · T whole page · C compare · F full size
← → or h l the right month · Shift the left · S swap · W wipe · T whole page · Esc back
Brand changes
Each row is a name, owner or logo change we've confirmed. The dates are the last capture before it and the first one after. A new page design on its own isn't counted. Spot one that's wrong? Use “Not a rebrand” on its row.
We spotted these but haven't confirmed them yet, so they aren't counted above.
Documentation timing
See whether Shark Jack Display's docs change before or after its release notes, release by release.
Documentation timing is included with Practitioner, Researcher and Business. When the docs come first, you can read about a change before it's announced.
See plans → Already subscribed? Sign in →We check each docs page on a fixed schedule, so every gap is a range rather than one number. A release we can't place on either side is shown as "Can't tell".
Releases
6 entries
No entries match these filters.
- November 20263
- October 20262
- June 20261
Articles
1 article · updated Nov 10, 2026Where Shark Jack Display turns up in what others publish: how-tos, attack reports that name it, and incident write-ups. A row says why it is here and quotes where the article names it; the link goes to the publisher.
Tutorials & guides 1
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.