SkillAgentSearch skills...

greynoise

Classify IPs as scanners or targeted attackers — filter alert noise

Install / Use

npx skills add taracodlabs/aiden --skill greynoise

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

83/100

Category

Security

Supported Platforms

Universal

Our assessment of greynoise

greynoise scores 83/100 on our quality scale, 921st of 1,096 Security skills we index.

Its SKILL.md is 3.7 KB long, well organised into 9 sections with 3 code examples: a solid amount of guidance for an agent.

It has 843 GitHub stars, a meaningful sign that others use it.

Substance
26/30
Structure
18/20
Description
12/15
Adoption
12/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so greynoise is actively maintained.
  • Our last check on 2026-11-07 found the source still online.
  • It is released under AGPL-3.0, a copyleft license: you can use it, but modified versions you distribute must carry the same license.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-06. Automated pattern scan on 2026-10-06. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

greynoise compared with similar skills

All 4 of these similar skills score higher than greynoise; compare them before choosing.

SkillScoreStarsUpdatedFormat
greynoise (this skill)by taracodlabs838432mo agoSKILL.md
Agent-Reachby Panniantong100112.7k9d agoCLAUDE.md
headroomby headroomlabs-ai10079.9ktodayCLAUDE.md
Scraplingby D4Vinci100103.9ktodayMCP Server
crawl4aiby unclecode10087.5ktodayMCP Server

Frequently asked questions

How do I install greynoise?
Run npx skills add taracodlabs/aiden --skill greynoise. The install tabs above show the steps for each supported agent.
Which AI agents does greynoise work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is greynoise safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is AGPL-3.0-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is greynoise still maintained?
The repository was last updated about 2 months ago, so greynoise is actively maintained.

name: greynoise description: Classify IPs as scanners or targeted attackers — filter alert noise category: security version: 1.0.0 license: Apache-2.0 origin: aiden tags: security, greynoise, scanner, threat-intel, ip, osint, soc, incident-response, noise-filtering env_required:

  • GREYNOISE_API_KEY

GreyNoise — Internet Scanner Intelligence

GreyNoise collects and analyses internet-wide scan traffic. It tells you whether an IP hitting your firewall is a known mass-scanner (benign research tool or malicious crawler) versus a targeted attacker — helping SOC teams filter out internet noise from real threats.

Community tier: The /v3/community/{ip} endpoint works with limited volume even without a key. Set GREYNOISE_API_KEY for higher rate limits.

When to Use

  • An IP triggers a firewall rule and you want to know if it is just background internet noise
  • SOC triage: is this alert a known scanner or a targeted attack?
  • Filter false positives from SIEM before escalating an alert
  • User asks "is this IP a scanner?", "is this noisy traffic?", "is IP X benign?"

How to Use

Check if an IP is a known internet scanner

$ip      = "71.6.135.131"
$headers = @{}
if ($env:GREYNOISE_API_KEY) { $headers['key'] = $env:GREYNOISE_API_KEY }

$result = Invoke-RestMethod -Uri "https://api.greynoise.io/v3/community/$ip" -Headers $headers
Write-Host "IP:             $($result.ip)"
Write-Host "Noise:          $($result.noise)"        # true = mass-scanner
Write-Host "RIOT:           $($result.riot)"         # true = trusted benign service
Write-Host "Classification: $($result.classification)"  # benign | malicious | unknown
Write-Host "Name:           $($result.name)"
Write-Host "Last seen:      $($result.last_seen)"
Write-Host "Link:           $($result.link)"
Write-Host "Message:        $($result.message)"

Triage a batch of IPs from a firewall log

$ips = @("1.1.1.1", "8.8.8.8", "71.6.135.131", "45.83.66.42")
$headers = @{}
if ($env:GREYNOISE_API_KEY) { $headers['key'] = $env:GREYNOISE_API_KEY }

foreach ($ip in $ips) {
    try {
        $r = Invoke-RestMethod -Uri "https://api.greynoise.io/v3/community/$ip" -Headers $headers
        $tag = if ($r.riot) { '[RIOT-trusted]' } elseif ($r.noise) { '[SCANNER]' } else { '[TARGETED?]' }
        Write-Host "$ip  $tag  $($r.classification)  $($r.name)"
    } catch {
        Write-Host "$ip  [ERROR]  $($_.Exception.Message)"
    }
    Start-Sleep -Milliseconds 200
}

Interpret the results

noise = true   → IP is a known mass-scanner (benign researchers, crawlers, etc.)
riot  = true   → IP belongs to a trusted service (Cloudflare, Google, AWS, etc.)
classification = "malicious"  → Known malicious scanner — block and investigate
classification = "benign"     → Probably safe background noise — may deprioritise
classification = "unknown"    → No data — treat with caution

Examples

"Is 71.6.135.131 an attacker?" → Returns classification: malicious, noise: true — known malicious scanner.

"This IP keeps hitting our web server — is it just background noise?" → noise: true means it is scanning the whole internet, not targeting you specifically.

"Is 8.8.8.8 a threat?" → riot: true — belongs to Google DNS, trusted RIOT (Rule It Out) list.

Cautions

  • Community endpoint returns limited data — GREYNOISE_API_KEY unlocks full context
  • noise: false and riot: false does not mean the IP is malicious — GreyNoise may simply have no data for it
  • Data reflects GreyNoise's scanner observations — gaps exist for low-volume IPs
  • Free community endpoint: ~50 lookups/day per source IP without a key

Requirements

  • No key required for low-volume community lookups
  • GREYNOISE_API_KEY — free community key at https://viz.greynoise.io/account

Related Skills

View on GitHub
GitHub Stars843
CategorySecurity
Updated2mo ago
Forks147

Languages

TypeScript

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions