Back to reports

ArchangelC2 Is the Sideshow: Behind the Custom Panel, an Industrial-Scale ScreenConnect Fraud Operation With 3,000 Pre-Staged Victims and 103 Relay Subdomains

PublishedApril 9, 2026

ArchangelC2 Is the Sideshow: Behind the Custom Panel, an Industrial-Scale ScreenConnect Fraud Operation With 3,000 Pre-Staged Victims and 103 Relay Subdomains

TL;DR

Following @whoamix302's lead on a new C2 framework at 45.88.186.147:1337, we found a Node.js panel called ArchangelC2 running with the default password admin, three test victims, and zero public reporting anywhere. That looked like the story — an undocumented C2 in early development.

It wasn't the story.

Digging into the IP's history revealed that ArchangelC2 is a 19-day-old side project built by an operator who has been running an industrial-scale ScreenConnect remote-access fraud campaign since November 2024. The real operation:

  • 103 unique subdomains under innocreed.com — an expired legitimate South Carolina warehouse business domain bought via Njalla privacy registration
  • 288 TLS certificates issued across the subdomain fleet
  • 22+ backend IPs across three hosting providers (HostPapa/Railnet, FEMO IT Solutions, 1337 Services)
  • 2,997 pre-generated ScreenConnect victim sessions currently live on two Cloudflare Pages phishing sites — docusign-efiles.pages.dev (1,998 sessions) and o-invoices.pages.dev (999 sessions) — both still returning 200 OK as of publication
  • Multiple parallel social engineering lures: DocuSign signatures, overdue invoices, SSA government benefits, Adobe Acrobat Reader
  • A single ConnectWise ScreenConnect Cloud instance (instance-w08c5r) tying the entire operation together — and providing the strongest attribution vector, since ConnectWise can identify the account holder

The ArchangelC2 panel is the operator's attempt to build proprietary C2 tooling to supplement or replace their dependency on abused legitimate ScreenConnect infrastructure. The three "victims" on the panel — the operator's own server, a cloud sandbox, and one possible real target — are from the first nine days of development. The operator's real victim count is in the hundreds to thousands, measured by the pre-staged session pool and 17 months of continuous operations.

What this report adds to the public record:

  • First public documentation of the ArchangelC2 framework — architecture, API surface, capabilities, and the default-password exposure
  • The full 103-subdomain infrastructure map of the innocreed.com ScreenConnect abuse operation, with per-subdomain IP mappings and certificate timelines
  • Identification of two live Cloudflare Pages phishing sites serving 2,997 ScreenConnect session URLs as of publication
  • The instance-w08c5r ScreenConnect Cloud instance ID as the primary attribution and disruption vector
  • A named victim organization ("BEE OFFICE") from a ConnectWise session company field leaked in a phishing URL
  • The complete 17-month operational timeline from domain acquisition through ArchangelC2 development

Hat tip to @whoamix302 for the original lead on the ArchangelC2 panel. If you've already published reporting on innocreed.com, the instance-w08c5r ScreenConnect instance, the Cloudflare Pages phishing domains, or the ArchangelC2 framework, please reply or DM — we'll update and credit.


The Misdirection — ArchangelC2

What we found first

FieldValue
IP45.88.186.147
Port1337
Panel titleArchangel C2 | Dashboard
BackendNode.js + Express + MongoDB
AuthJWT via /api/auth/logindefault password admin
FrontendSingle-page HTML + TailwindCSS (CDN)
WebSocketLive screen capture (base64 JPEG frames) + remote shell
ASNAS210558 (1337 Services GmbH)
Hostingrdp.sh — bulletproof RDP hosting, Hamburg, Germany
VPS provisioned2026-03-21 (per RDP certificate CN=rhythmic-dawn)
Dashboard last modified2026-04-03
Victims3

The panel is functional but basic. A single HTML file serves the entire dashboard. The API surface is minimal:

POST /api/auth/login          — password-only auth, returns JWT
GET  /api/dashboard/victims   — list all victims (Bearer token)
GET  /api/dashboard/logs/:id  — per-victim log entries
WebSocket                     — auth, screen, command, command_output, status

The implant workflow visible in the log data follows a three-stage pattern:

Infection → FullZip (comprehensive data extraction) → Live Mode (screen + shell)

The three "victims"

#PC NameUserOSLogsAssessment
1rhythmic-dawnAdministratorServer 201944Operator's own VPS — hostname matches the RDP cert CN
2AppOnFly-VPSAdministratorWindows 108Cloud sandbox — AppOnFly is a VPS provider
3ShagginWaggononmbmWindows 111Recent infection — 1 log entry (Infection only, no FullZip)

Activity spans April 1–9, 2026. All three are consistent with development testing, not a live campaign. The operator infected their own server first (rhythmic-dawn), then a cloud sandbox (AppOnFly-VPS), then either picked up one real victim or tested against another sandbox.

OPSEC failures on the panel

FailureImpact
Default password adminFull admin access to anyone who finds the panel
No TLS on port 1337JWT tokens, victim data, screen captures — all cleartext
CORS Access-Control-Allow-Origin: *Any origin can query the API
No rate limiting on loginTrivially brute-forceable
Self-infection as test victimLeaks operator hostname, OS, HWID

This is a developer who hasn't shipped production C2 before. The underlying ScreenConnect operation, by contrast, shows considerably more operational maturity.


The Real Operation — innocreed.com ScreenConnect Fraud

The domain

FieldValue
Domaininnocreed.com
Original ownerInnocreed — legitimate minority business enterprise, warehouse services, Simpsonville SC
Original usePackaging, repackaging, inspection, quality control, labeling for manufacturers
Last legitimate snapshot2021-12-06 (Wayback Machine)
Domain expired~2022 (business closed)
Re-registered2024-11-01
RegistrarTucows Domains Inc. (via Njalla privacy proxy)
RegistrantCharlestown, Saint Kitts and Nevis — offshore privacy registration
NameserversNjalla privacy DNS (1-you.njalla.no, 2-can.njalla.in, 3-get.njalla.fo)
Expires2026-11-01

The operator bought an expired legitimate business domain specifically for the credibility it carries. innocreed.com has a clean history in web archives, a real business behind the name, and domain age dating back to 2018. That history makes URL reputation engines and email filters less likely to flag it compared to a freshly registered random-string domain.

The ScreenConnect Cloud instance

The single most important IOC in this investigation:

Instance ID:  instance-w08c5r
Relay:        instance-w08c5r-relay.screenconnect.com
Port:         443

Every phishing URL in this campaign — across all social engineering themes, across all delivery domains, across all 2,997 pre-generated session GUIDs — connects back to this one ConnectWise ScreenConnect Cloud subscription. A consistent RSA public key across all URLs confirms a single operator account.

ConnectWise can identify the account holder from this instance ID. They can pull:

  • Account registration details (name, email, payment method)
  • Total session count (how many victims have connected)
  • Connection timestamps (when victims were active)
  • Active session data (which machines are currently connected)
  • Geographic distribution of victim connections

This is the attribution and disruption vector. Everything else in this investigation is circumstantial infrastructure mapping. The ScreenConnect instance ID is a direct line to the operator's identity through a legitimate US company's customer database.

The 103 subdomains

Between November 2024 and May 2025, the operator created 103 unique subdomains under innocreed.com, each serving as a dedicated ScreenConnect relay endpoint. Certificate Transparency logs show 288 total certificates issued across the fleet — a combination of initial issuances and renewals indicating active use.

The subdomain naming evolved over the campaign's lifetime, revealing the operator's thinking:

Phase 1 — Legitimate-sounding names (November 2024)

portal, webhook, secure, standup, support, access, console, cloud, connect,
docs, manage, reports, assets, updates, alert

Professional, plausible names that could pass casual inspection.

Phase 2 — Control-themed names (December 2024)

cloudcontrol, dcontrol, eucontrol, info, news, work, rev

Still professional, but the naming discipline is starting to slip.

Phase 3 — Handle-style names (December 2024–January 2025)

jrdevil, doxs, kimkom, kemoni, skully, djinhops, den-ars1, pamstage,
skoller, wizzord, vilingor, apolog

These read like usernames or aliases — possibly per-victim or per-campaign identifiers. expiredpanel-1 is notable: the operator named a subdomain after a panel that expired, suggesting they're cycling through infrastructure as it burns.

Phase 4 — Security-themed names (January–February 2025)

sec-ans, sec-nv, devsec, docs-sec, nc-sec, fv-dev, nk-sec, hn-sec,
nj-sec, fn-dev, pv-sq, ar-bn, vtsec, zdecode, g-sec, df-sec, reg, soc,
sic, jtsec, help, security, supportsec, itsec, fd-sec, pjsec, nlsec,
nbsec, vbsec, olsec, rvsec, isec, wsec, zsec, msec, rsec, fsec,
anse, csec, us-sec, m-sec

The *sec naming convention dominates the mature phase — 30+ subdomains with security-themed names, likely designed to look like legitimate security infrastructure in victim browser address bars and connection logs.

The hosting fleet

ProviderASNIPsRole
HostPapa / Railnet LLCUS107.150.0.{138,160,161,166,168,169,180,183,185,199,207,212,214,223,225,228} (16 IPs)ScreenConnect relay servers
FEMO IT Solutions LtdAS214351 (GB)62.60.226.{243,248,249,251,253} (5 IPs)ScreenConnect relay servers
1337 Services GmbH / rdp.shAS210558 (DE)45.88.186.147ArchangelC2 panel + historical ScreenConnect
NL-811-4002192.118.59.44Webhook / exfiltration endpoint

The operator spread infrastructure across three hosting providers in three countries, with the HostPapa fleet in the US providing the bulk of relay capacity. Sixteen IPs on a single /21 is a significant hosting footprint — that's not a free-tier operation. Someone is paying real money for this infrastructure.


The Live Phishing Sites — Still Serving 2,997 Victim Sessions

This is the part that requires immediate action. Two Cloudflare Pages phishing sites are still live and returning 200 OK as of publication:

docusign-efiles.pages.dev

  • Theme: DocuSign electronic signature
  • Payload filename: Docusign_Signature.Client.exe
  • Download source: rvsec.innocreed.com
  • Pre-generated sessions: 1,998 unique ScreenConnect session GUIDs
  • Active: October 2025 – present

The page includes a config.js that stores an array of 1,998 unique ScreenConnect session URLs, each containing a different GUID. When a victim loads the page, JavaScript randomly selects a session from the pool and redirects the victim to download a ScreenConnect client pre-configured to connect to instance-w08c5r-relay.screenconnect.com using that specific session ID.

The per-session-GUID design means:

  1. Each victim gets a unique session — the operator can track individual compromises
  2. URL blocklists are ineffective — blocking one session URL doesn't affect the other 1,997
  3. Scale is pre-staged — the operator can compromise up to 1,998 victims without touching the phishing infrastructure

o-invoices.pages.dev

  • Theme: Overdue invoice notification
  • Payload filename: Invoice_Overdue.Client.exe
  • Download source: rvsec.innocreed.com
  • Pre-generated sessions: 999 unique ScreenConnect session GUIDs
  • Active: October 2025 – present

Same architecture, different social engineering theme, smaller session pool. Together, the two sites provide 2,997 total pre-staged victim sessions.

Why Cloudflare Pages?

The operator moved their phishing delivery from direct-hosted pages on innocreed.com subdomains to Cloudflare Pages sometime around October 2025. The advantages are clear:

  1. Free hosting — no financial trail to the hosting provider
  2. Cloudflare CDN — fast, reliable, globally distributed
  3. Legitimate TLS — Cloudflare-issued certificates, no self-signed cert warnings
  4. Takedown friction — Cloudflare Pages sites require abuse reports through Cloudflare's process, which is slower than a direct hosting provider takedown
  5. No server-side infrastructure — the phishing logic runs entirely in client-side JavaScript, making the page a static asset that's harder to fingerprint from the server side

A third variant, docusign-------e-file------signature.pages.dev, was active from October 2025 through January 2026 and appears to be an earlier version of the DocuSign theme.


The Social Engineering Lures

The operator runs at least five parallel social engineering themes, each targeting a different victim psychology:

1. DocuSign — "You have a document to sign"

The most scaled lure, with 1,998 pre-staged sessions. DocuSign is an ideal phishing vector because:

  • Victims expect to download and run something when signing a document
  • The "Docusign_Signature.Client.exe" filename maps to the mental model of "DocuSign client"
  • DocuSign notifications arrive via email constantly in business environments — one more doesn't raise alarms

2. Overdue invoices — "Payment past due"

The second-largest lure at 999 sessions. Urgency-driven social engineering targeting accounts payable workflows. Invoice_Overdue.Client.exe creates the impression that running the file will display the overdue invoice.

3. SSA government benefits — "Your Social Security statement"

Delivered via link.merakiasa.org URL shortener, the SSA-Statement.exe payload targets individuals expecting Social Security Administration correspondence. This lure targets a different demographic than the business-focused DocuSign and invoice themes — specifically older Americans and benefits recipients.

The merakiasa.org domain is a separate delivery vehicle — a URL shortener that redirects to the ScreenConnect download. The same domain was also used for Spectrum Webmail credential phishing, suggesting the operator runs credential harvesting alongside the remote-access fraud.

4. Adobe Acrobat Reader — "Install Adobe to view this document"

AdobeAcrobatReader.ClientSetup.exe served from services.innocreed.com at 62.60.226.249. The ConnectWise session URL for this variant included c=BEE%20OFFICE — a session company field that reveals the specific organization being targeted. "BEE OFFICE" is a named victim.

5. Generic support — "Remote support session"

The earliest variant: support.client.exe served directly from sec-ans.innocreed.com. This is the default ScreenConnect client naming pattern, used before the operator started wrapping the client in themed filenames. First detected by URLhaus on April 15, 2025.


Operational Timeline

Pre-history (2018–2022)

innocreed.com is a legitimate minority business enterprise in Simpsonville, South Carolina. Wayback Machine snapshots from 2018 and 2019 show a warehouse services company offering packaging, repackaging, inspection, quality control, sequencing, and labeling for manufacturers. The domain expires around 2022 after the business closes.

Phase 1 — Domain acquisition and infrastructure build (November 2024)

2024-11-01: innocreed.com re-registered via Tucows/Njalla with Saint Kitts and Nevis privacy registration. The operator chose this domain specifically for its legitimate history and clean reputation.

2024-11-01 to 2024-11-29: First 14 subdomains created (portal, webhook, secure, standup, support, access, console, cloud, connect, docs, manage, reports, assets, updates, alert). Each subdomain gets a dedicated ScreenConnect relay instance. The webhook subdomain at 92.118.59.44 serves as the exfiltration endpoint.

Phase 2 — Rapid scaling (December 2024 – February 2025)

33 new subdomains in December, ~30 in January, ~24 in February. The operator averages 2-3 new relay instances per day during peak scaling. Infrastructure diversifies across HostPapa/Railnet (16 IPs) and FEMO IT Solutions (5 IPs).

The naming convention evolves from professional-sounding (cloudcontrol, eucontrol) to handle-style (jrdevil, skully, djinhops) to security-themed (sec-ans, vtsec, nbsec, rvsec). By February 2025, the *sec naming pattern dominates — 30+ subdomains designed to look like legitimate security infrastructure.

expiredpanel-1.innocreed.com appears in this period, indicating the operator has already burned and rotated at least one relay instance.

Phase 3 — Active operations and first detection (March – May 2025)

2025-04-15: First public detection. URLhaus flags sec-ans.innocreed.com serving support.client.exe from 45.88.186.147 on port 443. This is the same IP that now runs ArchangelC2 — at that time, it was running a ScreenConnect relay.

2025-05-15: services.innocreed.com at 62.60.226.249 serves AdobeAcrobatReader.ClientSetup.exe targeting "BEE OFFICE".

2025-05-17: Last certificate issued for an innocreed.com subdomain (zen-doc). After this date, no new subdomains appear in Certificate Transparency — the operator stops expanding the innocreed.com fleet.

Phase 4 — Cloudflare Pages migration (October 2025 – present)

The operator shifts phishing delivery from direct innocreed.com hosting to Cloudflare Pages static sites. This represents a significant operational evolution: moving the victim-facing infrastructure to a free, CDN-backed, abuse-resistant platform while keeping the ScreenConnect relay backend on the existing infrastructure.

docusign-efiles.pages.dev and o-invoices.pages.dev go live with a combined 2,997 pre-generated ScreenConnect session URLs pointing at rvsec.innocreed.com.

Phase 5 — ArchangelC2 development (March – April 2026)

2026-03-21: New VPS provisioned at 45.88.186.147 from 1337 Services / rdp.sh. RDP certificate issued for hostname rhythmic-dawn.

2026-04-01: ArchangelC2 goes live. Operator self-infects as first test victim.

2026-04-03: Dashboard HTML finalized. Second test victim (AppOnFly cloud sandbox).

2026-04-09: Investigation date. Three victims on the ArchangelC2 panel, two Cloudflare Pages sites still live with 2,997 sessions, innocreed.com subdomains' DNS removed but the domain itself still registered through November 2026.


The Adjacent IP — typrocess.in

45.88.186.142 — five IPs away from the ArchangelC2 server on the same /24 — hosts typrocess.in, a domain registered via Namecheap with Namecheap email forwarding. The site runs a "Dashboard - DayNight Admin" template (TemplateMo 608) on Apache 2.4.63 / Ubuntu. It appears to be another staging environment — an admin panel template deployed but not yet operational.

The proximity on the same bulletproof hosting /24, combined with the operator's demonstrated pattern of maintaining multiple parallel infrastructure components, makes co-ownership plausible but unconfirmed. typrocess.in warrants monitoring for future activation.


Operator Profile

Operational maturity: MEDIUM-HIGH

The ScreenConnect operation demonstrates genuine tradecraft:

  • Expired legitimate domain for reputation
  • Njalla privacy DNS with offshore registration
  • Multi-provider infrastructure across three countries
  • Per-victim session GUIDs for tracking
  • Phishing migration to Cloudflare Pages for takedown resistance
  • Five parallel social engineering themes targeting different victim demographics
  • 17 months of continuous operations without significant disruption

OPSEC failures

The maturity has cracks:

FailureImpact
Single ScreenConnect instance ID (instance-w08c5r)ConnectWise can identify the account holder
config.js publicly readable on Cloudflare PagesAll 2,997 session GUIDs are harvestable
"BEE OFFICE" company name in phishing URLNamed victim organization leaked
ArchangelC2 default password adminFull C2 access to investigators
Self-infection as test victimOperator hostname rhythmic-dawn exposed
Consistent RSA public key across all URLsConfirms single-operator attribution
expiredpanel-1 subdomain nameReveals operational awareness of burn cycles
All 103 subdomains under one domainSingle domain takedown impacts entire operation

The instance-w08c5r exposure is the critical one. Everything else is intelligence for mapping. The ScreenConnect instance ID is a direct path to the operator's real identity through ConnectWise's customer database.

Motivation

Financial fraud via remote access. The ScreenConnect deployment pattern — individual sessions per victim, multiple social engineering themes, named target organizations — is consistent with callback phishing / tech support fraud / BEC (business email compromise) where the operator gains remote desktop access to victim machines and then conducts fraudulent transactions, credential theft, or data exfiltration in real time.

The ArchangelC2 development suggests the operator wants to:

  1. Reduce dependency on ConnectWise — whose abuse team could terminate their account at any time
  2. Add capabilities beyond ScreenConnect's feature set — specifically the FullZip automated data extraction and live screen streaming that ArchangelC2 provides
  3. Own their infrastructure rather than routing through a legitimate vendor's cloud

Detection & Hunting

Immediate blocks

# ArchangelC2
45.88.186.147

# ScreenConnect relay servers (HostPapa/Railnet)
107.150.0.138   107.150.0.160   107.150.0.161   107.150.0.166
107.150.0.168   107.150.0.169   107.150.0.180   107.150.0.183
107.150.0.185   107.150.0.199   107.150.0.207   107.150.0.212
107.150.0.214   107.150.0.223   107.150.0.225   107.150.0.228

# ScreenConnect relay servers (FEMO IT)
62.60.226.243   62.60.226.248   62.60.226.249
62.60.226.251   62.60.226.253

# Webhook/exfil
92.118.59.44

# Adjacent
45.88.186.142

# Domains
innocreed.com
typrocess.in

# Phishing (STILL LIVE)
docusign-efiles.pages.dev
o-invoices.pages.dev
docusign-------e-file------signature.pages.dev

# URL shortener
link.merakiasa.org

# ScreenConnect relay
instance-w08c5r-relay.screenconnect.com

Hunting queries

  • ScreenConnect instance hunt — any ScreenConnect connection to instance-w08c5r-relay.screenconnect.com is this operator's infrastructure. Block at the DNS and network level.
  • Filename huntDocusign_Signature.Client.exe, Invoice_Overdue.Client.exe, SSA-Statement.exe, AdobeAcrobatReader.ClientSetup.exe, support.client.exe — all associated with this campaign. These are renamed ScreenConnect client binaries.
  • Cloudflare Pages hunt — any *.pages.dev domain containing docusign, invoice, e-file, or signature in the subdomain is worth inspecting.
  • Certificate hunt — new crt.sh entries for any *.innocreed.com subdomain indicate the operator is re-activating relay infrastructure.
  • HostPapa IP hunt — outbound connections from corporate networks to the 107.150.0.0/21 range on ScreenConnect ports (443, 8040, 8041) are suspicious if your organization has no legitimate HostPapa services.
  • ConnectWise process huntScreenConnect.Client*.exe or ConnectWise*.exe processes launched from Downloads folders, temp directories, or browser cache locations rather than proper installation paths.
  • URL pattern hunt — ScreenConnect session URLs containing instance-w08c5r in the relay parameter.

Known file hashes

3a0173d1c1a5106e763abbd751e70b06bb1ae22489ed1876bbdef6d550446ca7  support.client.exe
c5e8a29f42c055a42869ece87fc2f43f1a0492213207f19e91e28bdaf9065c88  support.client.exe (variant)
3894f16277fa5c47...  SSA-Statement.exe (truncated — full hash in IOC file)
456b1e712e3321f9...  AdobeAcrobatReader.ClientSetup.exe (truncated)

Plus 21 additional unique hashes captured by URLScan across the campaign's lifetime.

ArchangelC2 panel signatures

For researchers hunting other ArchangelC2 deployments:

HTTP title:         "Archangel C2 | Dashboard"
API endpoint:       /api/auth/login (POST, JSON body with "password" field)
API endpoint:       /api/dashboard/victims (GET, Bearer token)
Log message:        "Infection successful, starting extraction..."
Log message:        "Archangel collection completed. Entering live mode..."
WebSocket types:    auth, screen, command, command_output, status
Server header:      Express (Node.js)

Confidence Table

ClaimConfidenceBasis
ArchangelC2 at 45.88.186.147:1337 is a custom, undocumented C2 frameworkHIGHFull source code scraped, zero prior public reporting
The same operator runs both ArchangelC2 and the innocreed.com ScreenConnect campaignHIGHSame IP (45.88.186.147) served both — ScreenConnect relay in April 2025, ArchangelC2 panel in April 2026
The ScreenConnect operation has been running since November 2024HIGHCertificate Transparency shows first cert for portal.innocreed.com on 2024-11-01
2,997 pre-staged victim sessions are currently liveHIGHCloudflare Pages sites returning 200 OK with full config.js contents as of investigation date
The operator's real victim count is in the hundreds to thousandsMEDIUM-HIGHInferred from session pool size, 17-month operational period, and multi-theme campaign; exact count requires ConnectWise data
"BEE OFFICE" is a targeted victim organizationHIGHCompany name in ConnectWise session URL parameter
ConnectWise can identify the operator via instance-w08c5rHIGHStandard ConnectWise Cloud account structure — instance ID maps to customer record
innocreed.com was deliberately chosen for reputationHIGHDomain has legitimate business history 2018–2022, re-registered post-expiration
typrocess.in at .142 is the same operatorMEDIUMSame /24, same bulletproof hoster, but no direct infrastructure link confirmed
ArchangelC2 is being built to replace ScreenConnect dependencyMEDIUMPlausible from the capability overlap (remote screen + shell), but could be a parallel tool for different use cases

Priority 1 — Immediate disruption

  1. ConnectWise — Report instance ID instance-w08c5r. Request account holder identification and immediate suspension. ConnectWise has an active abuse team and has historically been responsive to ScreenConnect abuse reports. This single action could disrupt the entire operation.

  2. Cloudflare — Abuse reports for docusign-efiles.pages.dev and o-invoices.pages.dev. These are actively serving phishing lures as of publication. Cloudflare Pages takedowns require abuse reports at https://abuse.cloudflare.com/.

Priority 2 — Infrastructure providers

  1. HostPapa / Railnet — 16 IPs in 107.150.0.0/21 serving as ScreenConnect relay infrastructure for a fraud campaign.

  2. FEMO IT Solutions — 5 IPs in 62.60.226.0/24 serving the same purpose.

  3. 1337 Services GmbH / rdp.sh45.88.186.147 running an open C2 panel with default credentials. This is a bulletproof hoster and is unlikely to act, but the report creates a paper trail.

Priority 3 — Victim notification

  1. "BEE OFFICE" — The named victim organization should be notified that they were specifically targeted by this campaign and should audit for ScreenConnect client installations.

Priority 4 — Domain and registrar

  1. Njalla / Tucowsinnocreed.com abuse report. Njalla is a privacy-focused registrar that explicitly markets to users wanting anonymity, so action is uncertain.

Prior art

  • @whoamix302 — original lead identifying ArchangelC2 at 45.88.186.147:1337
  • URLhaus community — first public flagging of sec-ans.innocreed.com / support.client.exe on April 15, 2025
  • ConnectWise/ScreenConnect abuse reporting — extensive prior public reporting on ScreenConnect abuse in callback phishing campaigns from Proofpoint, CrowdStrike, and others (this campaign appears to be a previously undocumented instance of the same TTP pattern)

If you've previously published reporting on innocreed.com, the instance-w08c5r ScreenConnect instance, the Cloudflare Pages phishing domains, or the ArchangelC2 framework, please reply or DM — we'll update and credit.


GHOST — Breakglass Intelligence "One indicator. Total infrastructure."

Share