Malicious IPs

Free feed of C2, scanner and malware-delivery IPs from Twitter/X researchers


Malicious IPs

C2, scanner and malware-delivery IPs from Twitter/X


IPs by window

Today

-

malicious IPs

Week

-

malicious IPs

Month

-

malicious IPs

Year

-

malicious IPs

What this list contains

  • Sourced from ~95 Twitter/X security researchers, refreshed every 15 minutes.
  • C2 servers, malware-delivery hosts, scanners and known abuse IPs.
  • IPv4 only in the current dataset. Onion infrastructure surfaced as URLs/domains, not IPs.
  • Caveat: many IPs sit on shared hosting or CDN ranges. Treat as enrichment signal, not standalone block decision.

Recent samples

Latest 10 IPs from the past 7 days. Live from api.tweetfeed.live/v1/week/ip.

Loading samples

Top tags for malicious IPs

Filter the IP feed by malware family or category. Each tag has its own landing page with recent samples and context.

  • #phishing
  • #c2
  • #cobaltstrike
  • #scam
  • #malware

See all tags on the Dashboard or browse the full IOC feed.

Frequently asked questions

What is a malicious IP feed?

A malicious IP feed is a continuously updated list of IPv4 addresses observed in adversary infrastructure. Common categories include C2 servers, malware-delivery hosts, port scanners and brute-force sources. Security teams ingest these into firewalls, IDS/IPS and SIEM correlation rules. TweetFeed publishes the IPs spotted by ~95 infosec researchers on Twitter/X, refreshed every 15 minutes.

How is this list updated?

Every 15 minutes. The pipeline scrapes RSS feeds from public Twitter/X researcher accounts and lists, extracts IPv4 addresses from tweets, deduplicates against the past year, tags them with malware family and category, and republishes the result in CSV, JSON and RSS.

Should I block these IPs at the firewall?

Block with caution. Shared hosting providers, CDNs and cloud platforms reuse IPs across legitimate and malicious tenants, so blanket blocking creates collateral damage. Use IP feeds as one signal among several: alert on connections, correlate with other indicators, and block only on high-confidence matches or in combination with active malicious activity from the same host.

Are these IPs verified malicious?

TweetFeed is OSINT, not a sandbox. IPs are sourced from public posts by infosec researchers, then deduplicated and tagged. False positives are higher for IPs than for URLs or hashes, especially when researchers post infrastructure observed for a single campaign that has since rotated. Cross-reference Shodan, AbuseIPDB or your sandbox before blocking.

What is the license? Can I use this commercially?

All TweetFeed IOC data, including this IP subset, is released under CC0 1.0 Universal (Public Domain Dedication). No attribution required, no warranty. Commercial use is allowed. The TweetFeed website code and branding are not covered by CC0.

License

Malicious IPs data: CC0 1.0 Public Domain. No attribution required, no warranty. Source code for the pipeline: github.com/0xDanielLopez/TweetFeed (MIT).