Kismet can function as a WIDS (Wireless Intrusion Detection System) with alerts for stateless and stateful fingerprint and trend based monitoring. Kismet fingerprint alerts can trigger on known-hostile specific behavior such as attacks against wireless drivers, and trend-based monitors can detect unusual behavior over time, such as flooding and denial of service attacks.

Kismet can integrate with other tools via the live packet export REST API, the Kismet alert REST API, and via syslog and some SIEM tools.

Kismet is most effective as an IDS in stationary (ie, non-wardriving) capacity. Kismet WIDS functionality can be used in mobile and channel-hopping installations, but accuracy and coverage may suffer.

Configuring alerts

Alert rates

Alerts are configured with the alert= configuration option, and the defaults are defined in kismet_alerts.conf. Alerts are configured by name, with throttle and burst options. They can be overridden with kismet_site.conf (preferred) or by editing kismet_alerts.conf directly (discouraged).

The throttle option controls how many alerts are allowed per time unit (seconds and minutes), and burst controls how many alerts are allowed in quick succession. For instance:


Will allow at most one alert per second, and at most 5 alerts per minute. Excess alerts will not be reported.

Complex alert configuration

Some alerts, such as APSPOOF, have additional configuration options. These options are documented in the description of each alert.

False positives

Kismet includes alerts for many theoretical attacks reported in research, as CVEs, etc.

Many of these attacks rely on a combination of specific chipsets and drivers, and specific abuses of the Wi-Fi standard; as Wi-Fi evolves, what was previously an over-long packet element used to exploit a driver may become a commonly used field which needs extra data.

Deprecated attacks in Kismet are typically disabled by default in the config file, but at times a new evolution or use of Wi-Fi will trigger an alert with a false positive.

Generally speaking, it is unlikely that most users will encounter cutting edge attacks in the wild. Many things are possible - which is why Kismet provides the alerts - but often unlikely. When given an usual alert, consider taking the step of examining the PCAP log directly with a tool like Wireshark.


ADVCRYPTCHANGETrend / StatefulIEEE80211 / Wi-Fi

An advertised SSID has changed the encryption options it is advertised with.

This can occur when an access point is reconfigured, or if a managed access point is rebooted with different settings, but can also occur when there is a spoofing attack such as evil twin which did not fully copy the attributes.

AIRJACKSSIDFingerprintIEEE80211 / Wi-Fi


One of the original 802.11 hacking tools, Airjack, set the initial SSID to airjack when loading.

This alert is no longer relevant since the Airjack toolset has long been discontinued, and is left for historical reasons.

APSPOOFFingerprintIEEE80211 / Wi-Fi

A list of valid MAC addresses for a given SSID can be configured via the apspoof= configuration option.

If a beacon or probe response for that SSID is seen from a MAC address not found in that list, an alert will be raised.

This can be used to detect spoofed or evil twin attacks and attacks like Karma, however it will not detect attacks which also spoof the MAC address.

The apspoof= configuration can specify exact string matches for the SSID, regular expressions using PCRE syntax, and single, multiple, or masked MAC addresses:


When providing multiple MAC addresses, they must be enclosed in quotes.

MAC addresses can be masked, where they match multiple addresses. MAC address masking works along the same logic as netmasks, where the common component is compared using the mask.

To match, for instance, all MAC addresses of the OUI 00:11:22:xx:xx:xx:

BEACONRATETrend / StatefulIEEE80211 / Wi-Fi
The advertised beacon rate of a SSID has changed; in a managed enterprise environment this may indicate a normal configuration change, however it may also indicate a spoofing attack such as evil twin which did not properly copy the attributes of the original access point.
BCOM11KCHANTrend / StatefulIEEE80211 / Wi-Fi

The chances of this attack being seen in the wild are quite rare.

Invalid channels in 802.11k neighbor report frames can be used to exploit certain Broadcom HardMAC implementations, typically used in mobile devices, as described in project zero 1289

The Bleedingtooth attack exploits vulnerabilities in the Linux Bluetooth stack which could lead to code execution. It can be detected when using a BTLE-capable capture data source, such as the CC2540, NRF, and similar. It can not be detected in HCI scan mode or with a Wi-Fi datasource.
BSSTIMESTAMPTrend / StatefulIEEE80211 / Wi-Fi
Invalid or out-of-sequence BSS timestamps can indicate AP spoofing. APs with fluctuating BSS timestamps could be an indication of spoofing or an “evil twin” attack. Out-of-order packets from multiple datasources and some AP firmware can both lead to false positives.
CHANCHANGETrend / StatefulIEEE80211 / Wi-Fi
A previously known Access Point has changed the advertised channel. For a managed Access Point or one with automatic channel selection, this may be normal, however it may also indicate a spoofing attempt where an Access Point is cloned to another channel.
CRYPTODROPTrend / StatefulIEEE80211 / Wi-Fi
A previously known Access Point has started advertising a less effective security suite. Generally, an AP should not change encryption settings or downgrade security, and this may indicate an attempt to spoof the AP with a cloned, weaker copy.

By spoofing disassociate or deauthenticate packets, an attacker may disconnect clients from a network which does not support management frame protection (MFP); This can be used to cause a denial of service or to disconnect clients in an attempt to capture handshakes for attacking WPA.

Typically small quantities of deauthenticate or disassociate packets are a normal part of Wi-Fi, but many denial of service tools send floods of these packets to prevent a client from reconnecting.

This alert may be impacted by the packet de-duplication feature; setting packets_dedup_size=0 in the Kismet configuration file may be required to full coverage with this alert.


A client which sends a DHCP DISCOVER packet containing a Client-ID tag (Tag 61) which doesn’t match the source MAC of the packet may be doing a DHCP denial-of-service attack to attempt to exhaust the DHCP pool.

To detect the DHCP client ID, the network must be unencrypted so that data may be observed.


Clients which request a DHCP address and receive a response, but operate on a different IP address, may be misconfigured, or may be spoofed by an attacker trying to gain access by simulating an existing client.

To detect the DHCP responses, the network must be unencrypted so that the data may be observed.

DISASSOCTRAFFICTrend / StatefulIEEE80211 / Wi-Fi

A client which has been disassociated from a network legitimately should not immediately continue exchanging data, as it needs to reestablish the connection to the AP. A client behaving oddly can indicate a spoofed client attempting to incorrectly inject data into a network, or a client which is the victim of a denial-of-service attack.

This alert may trigger a false positive when combined with channel hopping where the re-association is not seen.

DISCONCODEINVALIDTrend / StatefulIEEE80211 / Wi-Fi

The 802.11 specification defines valid reason codes for disconnect and deauthenticate events.

Various clients and access points have been reported to improerly handle invalid/undefined reason codes, and illegal reason codes may be an indicator of a spoofing attack.

Some devices have been observed using non-documented reason codes to no ill effect.


The DHCP configuration protocol allows clients to optionally include the desired hostname and the DHCP client vendor/operating system in the DHCP Discovery packet. These values should only change if the client has changed drastically (such as a dual-boot system). As these are typically rare, these values changing can indicate a client spoofing attack.

To detect the DHCP responses, the network must be unencrypted so that the data may be observed.

DOT11DTrend / StatefulIEEE80211 / Wi-Fi

802.11d country codes have been deprecated by the IEEE and the FCC, but are still broadcast by many devices and processed by many clients.

Conflicting 802.11d elements can indicate an AP spoofing attack where the cloned AP is not configured for the same regional restrictions.

FORMATSTRINGTrend / StatefulIEEE80211 / Wi-Fi

Added: 2021-07

While the 802.11 standard doesn’t place restrictions on what data can be in a SSID, the percent sign format indicators used by several programming languages have been used to crash devices such as iPhones and macOS systems.
KARMAOUIFingerprintIEEE80211 / Wi-Fi
Some implementations of the Karma attack, or hardware such as the WiFi Pineapple, use a predictable OUI of 00:13:37:… when spoofing responses.
LONGSSIDFingerprintIEEE80211 / Wi-Fi

The 802.11 specification allows for a maximum of 32 bytes for the SSID. Over-sized SSIDs are indicative of packet corruption, a significantly malfunctioning device, or of an attack attempting a buffer overflow on the access point or client drivers.

Modern drivers should be immune to SSID length overflow attacks, but historically it has been used to trigger bugs, crashes, and possible code execution.

LUCENTTESTFingerprintIEEE80211 / Wi-Fi


Very old 802.11b Lucent Orinoco cards generated identifiable packets in some scanning test modes.

These cards are extremely outdated and unlikely to be spotted in the wild at this point, but this alert is left for historical purposes.

MSFBCOMSSIDFingerprintIEEE80211 / Wi-Fi


Very old versions of the Windows Broadcom drivers cira 2008 did not properly handle SSID fields longer than 32 bytes, leading to code execution.

This vulnerability was implemented in the Metasploit framework.

These drivers are now extremely old and were only found on Windows XP systems, but this alert is left for historical purposes.

MSFDLINKRATEFingerprintIEEE80211 / Wi-Fi


Very old versions of the Windowd D-Link drivers did not properly handle extremely long 802.11 basic rate fields, leading to code execution.

This vulnerability was implemented in the Metasploit framework.

These drivers are now extremely old and were only found on Windows XP systems, but this alert is left for historical purposoes.



Very old versions of the Windows Netgear drivers did not properly handle unusually large beacon frames, leading to code execution.

This vulnerability was implemented in the Metasploit framework.

These drivers are now extremely old and were only found on Windows XP systems, but this alert is left for historical purposes.

NETSTUMBLERFingerprintIEEE80211 / Wi-Fi


The original Netstumbler tool on Windows could generate, in certain conditions, packets with identifiable content.

This alert only applied to extremely old versions of the tool, and is left for historical purposes.

NOCLIENTMFPFingerprintIEEE80211 / Wi-Fi

MFP (Management Frame Protection), or 802.11w, is standard for protecting clients and Access Points from spoofed management frames, such as those used for deauthentication and denial of service attacks.

Client MFP support is advertised in request packets as a client joins a network. When enabled, this alert will warn of clients which do not advertise support for MFP networks, which leaves them open to these attacks.

Despite MFP being adopted as part of WPA3 and WiFi 6e, widespread use is still uncommon; until then this alert may generate more noise than signal.

NONCEDEGRADEFingerprintIEEE80211 / Wi-Fi
A WPA handshake with an empty NONCE was observed; this could indicate a WPA degradation attack such as the vanhoefm attack against BSD.
NONCEREUSEFingerprintIEEE80211 / Wi-Fi
A WPA handshake has attempted to re-use a previously seen nonce value; this may indicate an attack against the WPA keystream such as the vanhoefm KRACK attack.
NULLPROBERESPFingerprintIEEE80211 / Wi-Fi


Probe response packets with a SSID element with a length of zero would cause the firmware in extremely old 802.11b network cards (Prism2, Orinoco, and the original Apple Airport) to crash.

Since then, packets with a zero-length SSID probe response have become common, and a normal part of the protocol.

This alert is left for historical purposes, but is disabled.

OVERPOWEREDFingerprintIEEE80211 / Wi-Fi

This alert is raised if the reported packet signal levels are abnormally high.

This can be caused by using an external amplifier, or by capturing while extremely close to the transmitter.

Over-amplified signals can result in distortion and noise, leading to overall fewer packets captured. In the absolute worst case, using too powerful an amplifier too close to the transmitter may damage your Wi-Fi capture devices.

This alert is informational only, and relies on the reported signal levels from the capture layer.

PROBECHANTrend / StatefulIEEE80211 / Wi-Fi

Wi-Fi Access Points advertise a channel in the beacon packet; they may also include a channel in the probe response.

The probe response should match the advertised beacon channel; if it does not, this can indicate a spoofing or ’evil twin’ attack, but may also indicate a misconfigured or misbehaving Access Point or repeater.

PROBENOJOINTrend / StatefulIEEE80211 / Wi-Fi


Active scanning tools constantly send network discovery probes but never join any of the networks which respond.

This alert can cause excessive false positives in busy environments, and the general usage of Wi-Fi no longer matches the limited use patterns when this alert was first written, but it remains for historical reasos.

QCOMEXTENDEDFingerprintIEEE80211 / Wi-Fi

Added: 2019-08

Recent vulnerabilities found in the Qualcomm drivers for Android lead to code execution via over-sized IE 127 Extended Capabilities tags (CVE-2019-10539).

This alert detects packets with what appear to be over-sized IE 127 elements, however as the use of this tag evolves the size of the data continues to grow, false positives become more common.

This alert is disabled by default.

RSNLOOPFingerprintIEEE80211 / Wi-Fi
Invalid RSN (802.11i) security tags in a beacon frame can be used to cause loops and denial of service in some versions of the Atheros drivers, as described in CVE-2017-9714 and
RTL8195VD1406FingerprintIEEE80211 / Wi-Fi

A series of vulnerabilities in the RTL8195A Wi-Fi drivers can allow code execution without authentication, as described in CVE-2020-9395 and the VDOO paper here.

Over-sized EAPOL Key packets can be used to trigger overflows in the driver and gain code execution.

RTLWIFIP2PFingerprintIEEE80211 / Wi-Fi
A vulnerability in the Linux RTLWIFI driver could lead to code execution or a denial of service, as described in CVE-2019-17666 and the LKML mailing list. This attack involves malformed Wi-Fi Direct P2P Notification of Absence frames.
VDOO202027301FingerprintIEEE80211 / Wi-Fi
A vulnerability discovered by VDOO in the RTL8170C chipset could be used to execute code on the device with over-long key responses in the WPA handshake. This attack has not been seen in the wild yet, and requires knowledge of the victim devices WPA PSK. A WPA RSN key response with a total length over 0x101 bytes can be used to overflow a static buffer. The attack is described in CVE-2020-27301 and the VDOO report here.
VDOO202027302FingerprintIEEE80211 / Wi-Fi
A vulnerability discovered by VDOO in the RTL8170C chipset could be used to execute code on the device with over-long key responses in the WPA handshake. This attack has not been seen in the wild yet, and requires knowledge of the victim devices WPA PSK. A WPA RSN key response with AES encryption and a length over 0x80 can be used to overflow a static buffer. The attack is described in CVE-2020-27302 and the VDOO report here.
WMMOVERFLOWFingerprintIEEE80211 / Wi-Fi
The Wi-Fi standard specifies 24 bytes for WMM IE tags. Over-sized WMM fields may be an attempt to exploit bugs in Broadcom chipsets, such as the Broadpwn attack.
WPSBRUTETrend / StatefulIEEE80211 / Wi-Fi

The WPS protocol has been shown to have numerous vulnerabilities, including errors in how the key exchanged is processed making it much weaker against brute force attacks.

Excessive WPS negotiation attempts may indicate a brute force attack such as Reaver against a WPS enabled Access Point.

WMMTSPECFingerprintIEEE80211 / Wi-Fi
Too many WMMTSPEC options were seen in a probe response; this may be triggered by CVE-2017-11013 as described at