NEWPractise supported commands in browser simulations, alongside the lesson.Try a browser practice exercise.Try a lab♥ Codelivly is 100% free, no paywall. If it helped you, chip in to keep it running.100% free. Help keep it so.Support us
Network Forensics
Network traffic is the nervous system of any organization, and for attackers, it is the highway used for initial access,
ViewAdvanced Static and Dynamic Analysis
This advanced learning path bridges the gap between foundational reverse engineering and expert-level malware analysis.
ViewUnpacking and Anti-Analysis Evasion
Master the techniques malware analysts use to unpack protected binaries and overcome anti analysis mechanisms. Learn how
ViewRecon & Enumeration Tools
Reconnaissance is the foundation of every successful penetration test. Amateurs treat it as a box-ticking exercise, runn
ViewExploitation Fundamentals
Amateurs stop at the proof of concept. They pop an alert(1), dump a database via SQLi, or find an IDOR, write a report,
ViewActive Directory Attacks
A comprehensive, advanced learning path covering the core methodologies of Active Directory exploitation. Progress from
ViewPreview · 30 min
Stop getting blocked by default scans. Master Nmap evasion techniques like packet fragmentation, decoy routing, and timing manipulation to bypass IDS/IPS sensors and map heavily defended networks.
IP packets are allowed to be split into fragments and reassembled by the receiver - this is a normal, legitimate part of the protocol, used whenever a packet is larger than the path's maximum transmission unit (MTU). The problem for a defender is that some intrusion detection systems inspect each fragment on its own, before reassembly, to save processing time. If an attacker deliberately splits a probe into unusually tiny fragments - for example, 8 bytes each, far smaller than any real MTU constraint would ever produce - a full signature (which might be 20+ bytes long) is never present in any single fragment, and a naive IDS never matches it.
The fix is on the defender's side, not the attacker's: configure the IDS/firewall to reassemble fragmented traffic before running signature matching (most modern IDS engines support this directly), and separately, treat an abnormally small average fragment size - well below anything normal traffic produces - as suspicious on its own, regardless of what the reassembled payload turns out to be.
Create a free account to unlock the rest of this task, complete tasks, and earn Rep.
Sign in