Skip to content
NewCybercrime Report 2026 · Eight Chapters · A Post Is Not An Incident → Explore The ChaptersCybercrime Report 2026 → Explore
All short reads
Short readCommodity malware4 min read

Emotet and Ramnit Feeds: Seven Relay Candidates, 908 Held Rows

By
Odin by Brandefense
Published
19 November 2026
Reading time
4 min read
Short version of the full report · 19 min readLoader and Stealer Feeds: Seven Relay Candidates, 908 Held Rows

Key takeaways

  • Only seven dedicated cloud and VPS endpoints across six IPv4 addresses survived collision filtering across 3,500 examined rows, and all six addresses remain withheld pending independent C2 corroboration.
  • All 700 examined Ramnit endpoints (from 6,804 global sightings) carry an upstream victim label and were withheld; infection or sinkhole status was not verified on every host.
  • Two hundred eight examined endpoints sit on broadband telecom carriers or shared Cloudflare (73) and Akamai (21) edge proxies.
  • Twenty-seven of 34 feed-labelled confirmed rows failed review due to victim tags, broadband telecom listings, financial-lure certs, or port 3389 RDP collisions.
  • Avoid static IP blocks from uncorroborated feed exports, and catch loader and stealer traffic using HTTP, SOAP, and endpoint process rules.

Only seven of 3,500 examined endpoints remained as cloud or VPS relay candidates without independent C2 corroboration; 908 hit victim-labelled, ISP, or CDN collision rows. In practice, a cyber threat intelligence platform can help defenders separate rented attacker servers from home broadband routers, Cloudflare reverse proxies, and victim-labelled customer networks in unverified feeds. Blocking every listed address creates self-inflicted outages while missing panels that defenders can review with external attack surface management.

Odin by Brandefense analyzed 3,500 endpoints across 3,311 hosts from 11,819 global feed sightings in the two weeks ending 21 November 2026. Only 247 sampled rows had last-seen dates in that window; 3,253 were older feed listings.

Only seven dedicated cloud and virtual private server endpoints across six unique IPv4 addresses survived initial collision checks, and none had independent C2 beacon or protocol proof. All 3,500 examined endpoints across 3,311 hosts therefore stay withheld from public block lists to protect victim-labelled hosts, telecom users, shared CDN proxies, and unverified tenants.

The full report carries the hosting breakdown, eight published JARM indicators, five wire signatures, and four deployable rule files; the Odin Research blog collects related cases.

Figure 1: Victim botnet feeds and ISP relays dwarf seven cloud and VPS relay candidates
Figure 1: Victim botnet feeds and ISP relays dwarf seven cloud and VPS relay candidates

Why do Ramnit and Emotet feeds blackhole innocent networks?

More than half of all sightings in our study (6,804 of 11,819, or 57.6%) carry a Ramnit label under an explicit victim category. Across 700 examined Ramnit endpoints on 599 hosts, exposed ports belong to ordinary FTP, web, and router services. These include ports 21, 80, 81, 82, 88, 8081, and 8088.

Four Ramnit entries even carried a "confirmed" tag despite sitting on victim-labelled FTP and telecom hosts in China and Thailand. Overall, 93.6% of examined Ramnit rows sit in China (438), South Korea (161), Thailand (34), and Indonesia (22). Blocking a Ramnit feed cuts off 599 victim-labelled hosts instead of an attacker server.

A second collision pool spans 208 endpoints across 42 broadband telecom and shared CDN networks:

  • 73 LokiBot endpoints resolve to Cloudflare, Inc. anycast addresses, where static IP blocks cut off thousands of benign websites while leaving the origin PHP server online.
  • 66 Emotet-labelled endpoints sit on telecom carriers (45) or Akamai Connected Cloud ranges (21). Infection and proxy behavior were not verified for each host.
  • 65 RedLine rows and 4 Raccoon rows sit on subscriber ISPs, led by 57 RedLine port 25920 leases on a national telecom carrier in Uruguay.
Figure 3: Why raw Emotet and Ramnit IP feeds blackhole innocent networks
Figure 3: Why raw Emotet and Ramnit IP feeds blackhole innocent networks

Why do even the six remaining cloud and VPS relays require corroboration?

Reviewing all 34 upstream "confirmed" records eliminated 27 rows (79.4%) on collision grounds. Those 27 rows included four victim-labelled Ramnit rows, two broadband Emotet listings, two Dutch port 3389 Remote Desktop collisions, six Huawei Cloud financial-lure rows, and 13 single-batch cloud rows.

Seven dedicated endpoints across six unique IPv4 addresses remained on commercial cloud and VPS providers. Independent protocol, beacon, or workbench C2 corroboration was not documented for those six addresses, so all seven endpoints remain withheld from static block lists:

FamilyEndpoint profile (address withheld)Hosting and countryReview finding
EmotetDedicated TLS port 443 endpointAmazon.com, Inc., USCustom domain cert and 29d29d07d29d JARM; C2 beacon uncorroborated
EmotetDual-port droplet HTTP port 80DigitalOcean, LLC, DECustom domain cert; independent HTTP POST C2 signal not documented
EmotetDual-port droplet HTTP port 8010DigitalOcean, LLC, DEAlternate port on the same German droplet; C2 uncorroborated
EmotetPaired US droplet #1 HTTP port 80DigitalOcean, LLC, USShared custom cert profile; independent C2 signal not documented
EmotetPaired US droplet #2 HTTP port 80DigitalOcean, LLC, USShared custom cert profile; independent C2 signal not documented
RedLine StealerHigh-port TCP 49157 endpointAmazon.com, Inc., GBDefault Windows host cert; WCF SOAP beacon not documented
RedLine StealerDedicated TCP 5800 endpointHetzner Online GmbH, FIPort 5800 listener; WCF SOAP payload not documented

How do you catch proxy-hidden stealers without blocking Cloudflare or ISPs?

Figure 5: Seven cloud and VPS relay candidates across 11,819 global sightings
Figure 5: Seven cloud and VPS relay candidates across 11,819 global sightings

Raccoon Stealer (700 examined rows, 97.9% on HTTP port 80, listed on or before December 2025) produced zero corroborated block-list servers. LokiBot (700 rows on ports 80 and 443, listed through May 2026) also produced zero corroborated block-list servers. Three Windows TLS JARM hashes also occur across 79 RedLine rows and 55 Ramnit victim-labelled rows. Instead of blocking recycled VPS or CDN addresses, inspect protocol payloads and process behavior:

  • RedLine WCF SOAP contracts: Alert on HTTP POST requests with SOAPAction header hxxp://tempuri[.]org/IRemoteEndpoint/ or XML methods CheckConnect and ScanResult.
  • LokiBot and Raccoon HTTP gates: Alert on /PvqDq929BSx_A_D_M_I_N_a.php, /fre.php posts with Charon; Inferno User-Agent headers, and POST /config bodies containing bot_id and config_id.
  • Emotet and RedLine host processes: Alert when regsvr32.exe or rundll32.exe connects to Emotet ports, or when .NET utilities open RedLine high ports.

Are these five families operated by one group?

No evidence links them to one operator. Zero hosts among all 3,311 distinct hosts carry labels from two families, and the 21 shared /24 blocks may reflect co-tenant VPS hosting. We present the five families as an analytical model to help teams separate durable C2 signals from victim and ISP noise.

What to do now

  • Do not import raw Emotet, RedLine, Raccoon, LokiBot, or Ramnit IP feeds into firewall block lists without an independent protocol, beacon, or endpoint signal.
  • Quarantine victim-tagged Ramnit feeds, broadband telecom ISPs, and Cloudflare or Akamai ranges out of automated firewall block lists.
  • Deploy the six Suricata 7 signatures from the full report's Detection rules tab to catch RedLine SOAP envelopes, LokiBot /fre.php gates, Raccoon /config check-ins, and Emotet POST beacons.
  • Enable the Sentinel KQL hunt and two Sigma rules to isolate Windows endpoints initiating suspicious regsvr32.exe, rundll32.exe, or .NET high-port connections.
  • Scan unpacked payloads and memory dumps with the three YARA rules for RedLine WCF configs, LokiBot gates, and Raccoon check-in parameters.

What is…?

Short explanations of the tools and families named in this study.

All explanations

Frequently asked questions

Why do Ramnit and Emotet feeds blackhole innocent networks?

More than half of all sightings in our study (6,804 of 11,819, or 57.6%) carry a Ramnit label under an explicit victim category. Across 700 examined Ramnit endpoints on 599 hosts, exposed ports belong to ordinary FTP, web, and router services. These include ports 21, 80, 81, 82, 88, 8081, and 8088.

Why do even the six remaining cloud and VPS relays require corroboration?

Reviewing all 34 upstream "confirmed" records eliminated 27 rows (79.4%) on collision grounds. Those 27 rows included four victim-labelled Ramnit rows, two broadband Emotet listings, two Dutch port 3389 Remote Desktop collisions, six Huawei Cloud financial-lure rows, and 13 single-batch cloud rows.

How do you catch proxy-hidden stealers without blocking Cloudflare or ISPs?

Raccoon Stealer (700 examined rows, 97.9% on HTTP port 80, listed on or before December 2025) produced zero corroborated block-list servers. LokiBot (700 rows on ports 80 and 443, listed through May 2026) also produced zero corroborated block-list servers. Three Windows TLS JARM hashes also occur across 79 RedLine rows and 55 Ramnit victim-labelled rows. Instead of blocking recycled VPS or CDN addresses, inspect protocol payloads and process behavior:

Are these five families operated by one group?

No evidence links them to one operator. Zero hosts among all 3,311 distinct hosts carry labels from two families, and the 21 shared /24 blocks may reflect co-tenant VPS hosting. We present the five families as an analytical model to help teams separate durable C2 signals from victim and ISP noise.

Read the full report · 19 min read

Loader and Stealer Feeds: Seven Relay Candidates, 908 Held Rows

In a two-week observation window ending 21 November 2026, Odin by Brandefense examined 3,500 endpoints across 3,311 hosts from 11,819 sightings labelled as Emotet, RedLine Stealer, Raccoon Stealer, LokiBot, and ...

Full report, 8 indicators and detection rules