PAGES
← all tools
◆ Network Analysis & Monitoring

above

v2.8 open-source

Above is a network security sniffer that detects vulnerabilities in network equipment by analyzing traffic across up to 28 protocols without generating network noise.

Summary

Above is an open-source, free network sniffer that passively analyzes traffic to find vulnerabilities in network hardware, run as a command-line tool that requires root privileges to capture packets. Built on Scapy, it decodes up to 28 protocols spanning discovery protocols, dynamic routing, 802.1Q802.1QAn IEEE standard that adds a 4-byte VLAN tag to Ethernet frames, letting a single physical link carry traffic for multiple isolated networks. Cyber tools use it to capture or inject traffic on specific VLANs., name resolution, and SCADA traffic like S7COMM and ModbusTCP, and it can also analyze existing pcappcapA packet capture, recorded network packets that can be inspected later. Analysts use it to reconstruct communication and investigate protocol behavior or suspicious traffic. files rather than only live capture. Its README addresses pentesters and security engineers assessing network equipment for weaknesses such as exposed VRRPVRRPA network protocol (RFC 5798) that lets multiple routers share a virtual IP address, electing one as active so hosts keep a working gateway if the primary fails. credentials or rogue FHRP devices, work that otherwise spans several separate recon tools. It has had 13 contributors since its 2022 first commit, but activity has slowed to 6 commits in the past year and no release in the past 231 days.

Above is a network security sniffer that detects vulnerabilities in network equipment by analyzing traffic across up to 28 protocols without generating network noise.

How above helps

Which rogue devices are impersonating gateways on this network segment?

inspects captured VRRP, HSRP, and GLBP traffic for FHRP advertisements from unexpected sources, flagging the ones that don't match known legitimate routers

Are any first-hop redundancy protocols leaking credentials in plaintext?

decodes VRRPv2 packets on the wire and surfaces any authentication strings sent unencrypted

Which name resolution requests on this segment could be poisoned?

watches for LLMNR, NBT-NS, and MDNS broadcasts and reports the hosts still falling back to these protocols instead of DNS

What dynamic routing chatter is leaking across a segment that shouldn't see it?

decodes OSPF, EIGRP, and BGP frames from the capture and reports the routing exchanges visible to a passive listener on that segment

Is this switch port exposed to VLAN hopping or trunk negotiation abuse?

reads 802.1Q tags and DTP frames from the traffic to show whether trunking can be negotiated or VLANs enumerated from the port

Did an incident's packet capture contain any of these exposures, without needing to be back on site?

runs the same protocol decoding against a saved pcap file instead of a live interface, so a capture taken during an incident can be analyzed after the fact

all 4 features, with the evidence for each →

Languages

Not documented

Features

4 capabilities across 2 capability groups · 2 backed by code, an API document or a real run

Built from above's releases, docs, README and our own runs. “Seen” marks the month we first spotted a release the vendor didn't date. Group names and tags are our labels.

Compare with peers →

  • above covers 1 of the 34 network analysis capabilities we track.
  • above covers 1 of the 5 network observation capabilities we track.

What above offers you

  • Command-line interface
Packet capture (live and offline) 2 features Network analysis since 2023
Traffic recording and PCAP analysis shipped Allows users to capture live network traffic into PCAP files or analyze previously recorded captures to identify threats and vulnerabilities. 2 releases · 3 other sources · first seen Dec 2023

Shared capability: Packet capture (live and offline)

release

  • Adds --record-pcap flag to record live traffic directly into a .pcap file. vettel · Dec 2023 · source · release history
  • Adds --analyze-pcap <path> flag to analyze previously recorded .pcap files. vettel · Dec 2023 · source · release history

example

  • Inspect the contents of a previously captured traffic file to identify suspicious patterns. above --analyze-pcap capture.pcap vettel · Dec 2023 · source
  • Capture network traffic during an interaction and save it as a standard PCAP file for later inspection. above --record-pcap output.pcap vettel · Dec 2023 · source
  • Analyze existing pcap for vulnerabilities above --input hsrp.cap
Traffic sniffing verified Captures network traffic, requiring root privileges to operate. 1 other source · first seen Aug 2026

Shared capability: Packet capture (live and offline)

we ran it

  • The tool printed its banner (version 2.8.1, codename Rubens Barrichello) and immediately halted with a message stating that sniffing traffic requires root privileges. Aug 2026 · the full run
Network traffic analysis 1 feature Network observation since 2023
Protocol scanning and detection shipped Captures and analyzes network traffic across a wide range of supported protocols to detect security issues, vulnerabilities, or suspicious patterns. 9 releases · 2 other sources · first seen Nov 2023

Shared capability: Network traffic analysis

release 9 total

  • Adds HSRPv2 protocol support for detecting first-hop redundancy attacks. v2.8 · Mar 2025 · source · release history
  • Adds decoding of plaintext passwords found in VRRPv2 packets. v2.8 · Mar 2025 · source · release history
  • Adds vendor detection by MAC address to aid device fingerprinting during network reconnaissance. v2.8 · Mar 2025 · source · release history
  • Rewrites host discovery via Passive ARP for enhanced reliability. v2.7 · Aug 2024 · source · release history
  • Adds SNMP and RADIUS protocol support for network threat detection. v2.7 · Aug 2024 · source · release history
  • Adds new parsing capabilities for EAPOL, ARP, IGMP, DHCP, and ICMPv6 protocols. v2.5 · Mar 2024 · source · release history

docs

  • Network traffic sniffer that detects vulnerabilities in network equipment by passively analyzing up to 28 protocols including OSPF, HSRP, STP, and SCADA protoco

example

  • Scan for VLAN segmentation issues across all supported protocols in a single pass. above --protocol all --802.1q_tag <tag_id> capture.pcap vivid · Nov 2023 · source
Other / not yet classified 1 feature Features we have not matched to a capability yet. A suggested match is marked.
VLAN search verified Allows users to search for and identify VLANs on a network. 2 releases · 1 other source · first seen Nov 2023

release

  • Separates VLAN search into a dedicated function for improved modularity. v2.7 · Aug 2024 · source · release history
  • New 802.1q_tag argument allows searching specifically for 802.1Q tags to detect segmentation security issues on VLANs. vivid · Nov 2023 · source · release history

command line

Lines in monospace are the tool's own words: help text parsed from its source, or an endpoint from its API document. Under release, a line is our summary of a dated release. Under docs, it is quoted from the tool's own documentation or website. Each links back to the source it came from.

Score card

  1. Shipping velocity releases a month, last 12 months
  2. Documentation quality release-notes rubric, 0–100
  3. Breaking-change discipline how rarely a release breaks users, and notice given
  4. Maintenance risk quiet time against its own cadence, maintainers
  5. Innovation & surface new capabilities, API and MCP surface
  6. Community health
  7. Contributor trend distinct committers, this year against last
  8. Maintainer concentration bus factor now against a year ago
  9. Issue backlog trend issues closed per issue opened, 12 months
  10. Responsiveness median time to a maintainer’s first reply

Nine scores for above, 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 →

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 above 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…

Explore the full chart →

Releases

Show

6 entries

  1. March 20251
  2. August 20241
  3. March 20241
  4. January 20241
  5. December 20231
  6. November 20231
    Show

    6 entries

    Project health

    Issue, contributor and maintainer activity in caster0x00/Above, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.

    1. Contributors 1 −2 vs prior 12 months
    2. Maintainers 1 +1 joined · −2 left, last 12 months
    3. Bus factor 1 committers behind half the commits
    4. Community-filed not measured of issues opened, last 12 months
    5. Median time to close not measured issues closed, last 12 months
    6. Open backlog 0 of 4 issues ever filed
    1. Issues opened / month 0 · 0 communitymaintainers
    2. Open backlog 0
    3. Contributors / month 0
    4. Commits / month 0
    5. Stars 871
    Issue themes, last 12 months not measured

    Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this

    Add the badge to your README

    Maintain this project? The badge links readers straight to this page, so they can follow every release here.

    Tracked by Cyber Toolchain Choose a badge style and copy the code →
    browse all tools → score card for your toolchain →