abuseipdb-api
FreeAbuseIPDB API reference. IP reputation and abuse report lookups.
The English summary is being prepared. Showing the original description.
GreyNoise API reference. Internet scanner/noise classification for IPs.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
https://api.greynoise.io/v3/communityhttps://api.greynoise.io/v3Header: key: $GREYNOISE_API_KEY
curl -s "https://api.greynoise.io/v3/community/{ip}" \
-H "key: $GREYNOISE_API_KEY"
Response fields:
noise — true if IP is a known internet scannerriot — true if IP belongs to a known benign service (CDN, DNS, etc.)classification — benign|malicious|unknownname — actor name if identifiedlast_seen — last observation datemessage — human-readable summarycurl -s "https://api.greynoise.io/v3/noise/context/{ip}" \
-H "key: $GREYNOISE_API_KEY"
Additional fields: tags, cve, os, ports, raw_data
| Classification | Meaning | Action |
|---|---|---|
benign + noise:true | Known benign scanner (Shodan, Censys, etc.) | Likely false positive — deprioritise |
malicious + noise:true | Known malicious scanner | Real threat, but opportunistic, not targeted |
unknown + noise:true | Unclassified scanner | Investigate further |
noise:false + riot:false | Not a known scanner | May be targeted — investigate |
riot:true | Known benign service | Definitely deprioritise |
GreyNoise answers: "Is this IP scanning the whole internet, or is it specifically targeting us?"
noise:true → opportunistic, not targetednoise:false → potentially targeted, higher priorityip: <IP>
noise: <true/false>
riot: <true/false>
classification: benign|malicious|unknown
name: <actor name or "unknown">
last_seen: <date>
message: <summary>
verdict: benign-scanner|malicious-scanner|not-scanner|benign-service
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
AbuseIPDB API reference. IP reputation and abuse report lookups.
The English summary is being prepared. Showing the original description.
Analysis of Competing Hypotheses — structured technique for evaluating multiple explanations against evidence. Use when facing ambiguous attribution or multiple plausible scenarios. Prefers graded evidence items from /quality-of-information-check and runs that skill first when handed raw URLs or text. Runs on ungraded evidence when asked, labelled as such, unweighted, and capped at Moderate confidence.
The English summary is being prepared. Showing the original description.
Use when documenting a named campaign across time and victims, the user asks to start or update a campaign record, or another skill identified a multi-incident cluster that warrants formal tracking. Provides the template (timeline, attribution, victimology, attack chain, Diamond Model mapping, IOC clusters) and the lifecycle from active to historical.
The English summary is being prepared. Showing the original description.
Use when the user asks about carding, BIN attacks, payment-card breach markets, fullz/CVV2 trade, autoshops (BidenCash, Brian's Club, Russianmarket, B1ack's Stash), or financial-fraud TTPs. Self-updating knowledge cell.
The English summary is being prepared. Showing the original description.
Censys API v2 reference. Host reconnaissance and certificate data.
The English summary is being prepared. Showing the original description.
Use when the user asks about Chinese state-sponsored cyber operations or specific PRC-aligned actors (APT41, Volt Typhoon, Mustang Panda, APT10, APT31, Salt Typhoon, etc.), MSS/PLA-attributed campaigns, or PRC sector targeting. Self-updating knowledge cell.
The English summary is being prepared. Showing the original description.