The Innocent: The Legitimate Traffic in the Trap

TI-2026-075Y ยท The Armory, Part Y Confidence: HIGH โ€” direct honeypot classification + external corroboration Classification: TLP:WHITE

Not everything in the trap is hostile

Twenty-three letters of this series have studied attackers. It would be easy to assume that everything a honeypot catches is an attacker โ€” that a trap set for the offense captures only the offense. But a honeypot does not choose what connects to it; it catches whatever crosses its door, and a real fraction of that is not an attack at all.

The census is honest about this. A small population is classified benign. The honeypot's independent external reputation source, GreyNoise, tags a set of sources as benign of its own accord. And more than 1,100 connections arrive from Tor exit nodes โ€” traffic that is genuinely mixed, not inherently hostile. In a dataset built to study the offense, the presence of a labelled-innocent fraction is not an error or an embarrassment. It is the sensor being truthful about what the internet's background traffic actually contains: the legitimate alongside the hostile, arriving through the same door.

This final substantive letter is about that innocent fraction โ€” because it turns out to be the purest possible demonstration of the thesis the whole series has been building toward.

The researchers use the attackers' tools

Here is the fact that makes the innocent fraction so instructive. Legitimate internet-measurement projects โ€” Shodan, Censys, academic scanning groups at universities โ€” continuously sweep the entire internet, port by port, service by service, as a matter of routine and public good. It is how the security community knows what is exposed, how researchers study the internet's shape, how defenders find their own forgotten servers.

And they do it with the exact same tools the census has spent the whole series cataloguing. zgrab2 and masscan. The Go crypto/ssh library that powers the compiled swarm (075L). Nmap's enumeration scripts (075N). A Shodan scan of your SSH service and an attacker's reconnaissance of it present the same fingerprints โ€” the same HASSH, the same handshake โ€” because they are, quite literally, the same programs. The researcher measuring the internet and the attacker preparing to exploit it reach into the identical drawer.

So the honeypot's hardest classification problem is not some exotic evasion. It is this: the tool cannot tell you whether the scanner sweeping your port is Censys building a public dataset or an attacker building a target list, because at the level of the tool there is nothing to tell. This is The Weapon Is Never the Point (075I) โ€” the dual-use thesis โ€” encountered not as a philosophical claim but as a live, daily, operational problem. The artifact is genuinely unjudgeable. The same steel, in the researcher's hand and the attacker's.

What actually separates them

If the tool cannot distinguish the innocent scanner from the hostile one, what can? The same answer the series keeps arriving at from every direction: consent and behaviour.

A legitimate research scanner behaves like something with nothing to hide, because it has nothing to hide. It enumerates a service and moves on. It operates from declared, documented address ranges with reverse-DNS that names it โ€” census and shodan announce themselves in their own hostnames, precisely so that defenders can recognise them. It honours opt-out requests and exclusion lists. It respects rate norms. And, decisively, it never fires credentials at a stranger's login and never drops a payload. It measures; it does not enter.

An attacker does the opposite of every one of those things. It hides its origin rather than declaring it. It sprays passwords. It tries to walk through the door, not merely note that the door exists. It does not honour opt-outs because it never asked. The behaviour, not the tool, carries the intent โ€” and it carries it unmistakably, because the two behaviours diverge at exactly the point that matters: the researcher stops at measurement and the attacker proceeds to intrusion.

This is why the honeypot classifies on behaviour, and why it must. A classification built on the tool would fail in both directions at once: it would clear attackers who use benign-looking tools, and it would condemn researchers who use attack-looking ones. Only the act โ€” the presence or absence of the non-consensual attempt to enter โ€” sorts the innocent from the hostile. The census's benign fraction is the proof that it works: those are the sources whose behaviour, whatever their tools, never crossed the line from measuring to attacking.

Tor is a pipe, not an actor

The 1,100-plus Tor exit nodes deserve their own note, because they are a specific and common category error. It is tempting to treat every connection from a Tor exit as hostile โ€” the anonymity network has an unsavoury reputation, and attackers certainly use it. But a Tor exit node is a shared pipe, not an actor. It carries attackers who want anonymity, yes โ€” and also privacy-conscious legitimate users, researchers routing through Tor, and automated tools whose operators simply value not being tracked.

An IP being a Tor exit is not evidence of hostility. It is evidence that the true origin is hidden โ€” which is a genuinely different fact. Origin-hiding raises scrutiny; it does not establish intent. The right posture is not to blanket-block or blanket-condemn Tor exits (which would punish the legitimate along with the hostile), but to classify on the behaviour behind the exit, which the exit does not change. A Tor connection that enumerates politely is a researcher or a private user; a Tor connection that sprays credentials is an attacker. The pipe is the same; the act is what differs, once again.

Why the innocent fraction makes the whole program corroborate

The innocent fraction is also the standing reason the census never trusts its own single sensor. Because the honeypot's lone view cannot always tell research from attack, it resolves the ambiguous cases by external corroboration โ€” GreyNoise's benign/malicious verdicts, AbuseIPDB reports, published scanner ranges, the naming reverse-DNS of the big measurement projects.

This is the composite-signal method of The Sharpest Edge (075R) run in reverse. There, several independent sources agreeing that a node was malicious stacked into a high threat score. Here, several independent sources agreeing that a source is benign outweigh the honeypot's lone suspicion. The principle is symmetric and it is the ethical core of doing this work honestly: false positives are as real as false negatives. A threat program that only ever confirms guilt, and never innocence, is not rigorous โ€” it is credulous. The innocent fraction is the reason to check, the reason to corroborate benign as carefully as malicious, and the reason a single sensor's suspicion is never, in either direction, a verdict.

That matters beyond the honeypot. This series names real infrastructure and real behaviour; every letter has been careful to state what the evidence supports and no more. The Innocent is the letter that says why that care is not optional โ€” because the trap catches the legitimate along with the hostile, the tool cannot tell them apart, and the only honest way to sort them is on the act, corroborated across sources, with the humility to label a thing benign when the evidence says it is.

Reading the innocent โ€” for defenders

The armory is a catalogue of weapons, and it has been easy, across twenty-three letters, to treat every hand that touched one as an enemy. This letter is the necessary correction: some of the hands in the trap were measuring, not attacking, using the identical tools for the opposite purpose โ€” and the only thing that ever told them apart was what they did, not what they held. The dove and the hawk carry the same steel. You know which is which by watching where they fly, and by being honest enough to say, when the evidence supports it, that the thing in your trap did nothing wrong.

Indicators (TLP:WHITE)

IndicatorTypeMeaning
Source classified benign / GreyNoise-benignCorroborationThe honest innocent fraction โ€” not every connection is an attack
Declared range + naming reverse-DNS (shodan/censys)Benign signalLegitimate research scanner โ€” enumerates, does not enter
Identical tool (zgrab2/masscan/Nmap) for research and attackAnalysis ruleThe tool cannot classify โ€” judge behaviour and consent
Tor exit source (1,100+)Origin-hiddenA shared pipe, not an actor โ€” classify on behaviour behind it
Multi-source agreement on benignMethodComposite corroboration in reverse โ€” suppresses false positives

Cross-references

This dossier documents the legitimate, non-hostile fraction of honeypot traffic for defensive purposes, to underline that classification must rest on behaviour and consent rather than tool identity, and that benign must be corroborated as carefully as malicious. TLP:WHITE.

โš  Personal capacity. Research published independently โ€” not reflecting employer views. Derived from passive observation of attacks against personal infrastructure. Full disclaimer โ†’
โ† Previous The Armory โ€” 25 / 26 Next โ†’