EDR Bypass

Introduction

In 2025, Phishing remains to be an effective method for cybercriminals to compromise an organisation. Over the years we have seen a rise in phishing campaigns that utilise modern and advanced techniques such as Adversary-in-the-middle (AiTM). These advanced techniques have the capability to bypass traditional MFA, allowing attackers to steal credentials and maintain persistent access.

This report outlines a recent investigation that was carried out by Red Piranha’s Security Threat Researchers involving a sophisticated phishing campaign that’s targeting The Australian Legal Industry via Microsoft Office 365 environments, this campaign utilises advanced techniques including adversary-in-the-middle that can greatly increase the likelihood of gaining unauthorised access to a target environment. Red Piranha is a world leader in the collection and processing of threat intelligence and is currently the only company in the APAC region that is a member of the Cyber Threat Alliance based out of Washington DC.

This investigation was initiated after we were notified of a successful email phishing campaign that had targeted and exploited an Australian Legal Law office linked to our client. While the initial investigation focused solely on that incident, once we discovered how this group was operating and due to this group being relatively undetected throughout their entire operation we decided to do a thorough investigation into this emerging threat actor group.

Further analysis of this campaign revealed indicators that it is linked to a previously unknown phishing-as-a-service provided SAIGA Group, they’re an APT group that primarily operates out of telegram and has been active since at least January 2024. We were unable to complete attribution to this group, however, based on information we have obtained there are clear indicators that at least some of the core members are based out of Nigeria.

SAIGA Group started out by providing “bulletproof” VPS servers and shared hosting as well as being heavily involved in financial crime. By mid-2024, they shifted focus to phishing related services and their phishing-as-a-service solution SAIGA Hub. The phishing services and infrastructure they provide are vastly more expensive than most other solutions provided by other groups. Initial configuration and setup of the phishing infrastructure can cost up to $2,000 USD with a recurring monthly “maintenance” payment of $600 USD.

Successful logins and credentials are logged to a private Telegram chat between the bot and owner of that phishing domain, due to some poor design choices of the phishing infrastructure and related code, they made it quite trivial to find other phishing domains as well as the telegram bot tokens it is linked to. Throughout our investigation we have discovered 123 separate domains being used as well as at least 70 active telegram bots. This operation appears to be ramping up as new domains are discovered each day.

In response to this emerging threat, we have blocked access to all domains and services being used on all Crystal Eye appliances and have shared the intelligence we have obtained with the broader community. Indicators of compromise (IoCs), including domain names, IP addresses and hashes relating to this phishing campaign can be found in the table below.

To prevent your organisation from becoming the next victim by these advanced phishing attacks. It is recommended to enforce conditional access policies such as requiring location or device-based policies, and to implement phishing resistant authentication methods such as FIDO2 passkeys, certificate-based authentication or Windows Hello. Deployment of threat intelligence into the network stack with a TDIR program can assist in detection of these multistage attacks. Regular security awareness and training for all employees can ensure that everyone remains up to date with the latest threats.

Initial Investigation

In mid-February 2025, we were notified of a phishing email that was sent to one of our clients. The email phishing campaign had successfully targeted and exploited an Australian Legal Law office linked to this client.

After we completed an initial investigation of the phishing email and related infrastructure, we had some early indicators of how this group was operating. Due to there being no previously public information about this specific campaign, and it appears to be a fresh campaign, we took it upon ourselves to conduct a further investigation into this group.

Figure 1: Initial Email


The initial email contained both company logos, and a signature which was identical to emails sent within the targeted organisation. The view documents button in the previous screenshot linked to a suspicious looking google sites page.

 

Figure 2: Google Sites page from initial email


There was no additional information on that google sites page, and instead the PDF-Attachment button simply linked to the actual phishing domain which we will describe in the next section.

Phishing Page Interaction

The initial interaction with the phishing site may vary between domains depending on if Cloudflare turnstile is enabled.  If the Cloudflare turnstile is enabled, then you may be prompted to complete the Cloudflare captcha before continuing. If this is disabled visiting the phishing site will simply provide you with a Microsoft login that’s almost identical to the real site.

Figure 3: Cloudflare Turnstile


Figure 4: Microsoft Cloudflare Turnstile

Figure 5: Fake Microsoft Login form


The interaction with the phishing site works as follows:

  1. Site loads various files; attach,loading.htm, JavaScript files, etc
  2. Sends a POST request to an API endpoint (/api/config) that returns the phishing site configuration. This response includes the following:
    • Background Images, colours, userId, domainId, telegram chatId and bot tokens, Cloudflare key, creation and update timestamps, redirection URLs, blocked IPs, etc
    • Telegram Chat notification is sent containing visitor information.
  3. After entering an email in the form, the site sends a POST request to /api/email/, which assumably proxies the initial email input to login.microsoft.com to verify the email exists, if the email exists it will return a password field as well as cookies and other information that is retrieved from login.microsoft.com. Based on the information sent and received, this will likely return company logos if the email is linked to an organisation. This response contains the following:
    • Message, sFT (FlowToken), sCtx (wctx/estsrequest), canary, sessionId, bannerLogo, bannerIllustration.
  4. Upon entering the password, a POST request is sent to /api/login/. This request contains the email, password, and relevant Microsoft cookies used in the transaction, as well as the telegram chat and token information.  This login is once again proxied through to the Microsoft website, this is the final check that confirms if the credentials are valid or not.
    • If the credentials are invalid, access_denied is returned in the response. The invalid credentials are still sent in a telegram notification with the email, password, ip/ISP information.
    • If the credentials are valid, both the login details as well as the cookies obtained are sent in a telegram notification. 
  5. If valid credentials are entered, login information as well as the cookies are sent in a telegram notification. As the login process has already occurred and was successful, these cookies/session tokens can be used by the attacker to access the email account without needing to go through the login process again. This file contains the following cookie information retrieved from the login process:
    • ESTSAUTHPERSISTENT, ESTSAUTH, ESTSAUTHLIGHT, buid, CCState, SignInStateCookie, fpc, esctx, x-ms-gateway-slice, stsservicecookie
    • These cookies are then automatically set and used by the attackers as well as logged to the phishing console, this functionality allows these cookies to be used in the other tools within this phishing kit.


Figure 6: SAIGA Telegram Notification

Figure 7: Telegram Cookies ([email protected])


The SAIGA Connection

During our investigation of the previous phishing site interaction, we discovered several indicators that link this phishing campaign to a phishing-as-a-service (PaaS) provider known as SAIGA Group. As there is almost no public information about this group, we decided to conduct a much deeper investigation into who they are and how they operate.

Who is SAIGA Group?

SAIGA Group is an APT group that primarily operates out of telegram, they have remained relatively undetected throughout their entire operation.

The earliest known indicator of an operation relating to SAIGA Group dates to at least January 2024, this date is the creation date of the domain saiga-store-hub.com.

Through saiga-store-hub.com, SAIGA offered a range of web hosting services which included:

  • Bulletproof VPS Hosting
  • OpenXchange
  • Domain Registry
  • Bulletproof KVM RDP
  • Shared Hosting


Figure 8: SAIGA Store, billing.saiga-store-hub.com (web.archive.org)


It is currently unknown if SAIGA still provides web hosting solutions as this domain is no longer active.  

Since mid 2024, the primary operations of SAIGA Group shifted focus towards Phishing-as-a-service through the means of Saiga-hub (saiga-hub.ru, saiga-hub.com), registered in May 2024, and October 2024. Saiga Hub is where clients (threat actors) can access their phishing dashboard, configure settings related to their phishing campaigns, and can essentially be defined as a C2 server for all phishing services provided by SAIGA Group.  In the next section, we’ll dig deeper into the specific services SAIGA Hub offers.

How SAIGA Operates?

As previously mentioned, SAIGA primarily operates out of telegram where they advertise services relating to phishing and other financial crime. The services they provide can refer to the services provided on Saiga Hub and can include the following as per the advertisements and screenshots in telegram:

  • SAIGA Mailer
  • SMTP2SMS
  • 0.365 Sorter
  • Debouncer
  • FM Scanner
  • MX Sorter


Those are just the functionalities that are provided by Saiga-Hub, this group also offers a range of other services including:

  • Office 365 Phishing and setup ($2,000usd)
  • SAIGA Phishing page ($600usd/month)
  • Lead generation services (5000 leads/$200usd)
  • SMTP Servers
  • B2BxExtractor – SAIGA Email Extractor ($1000usd)
  • SAIGA All-in-one (SMTP2SMS, 0.365 Sorter, Debouncer, FM Scanner, MX Sorter) - $1k usd setup fee + $300 recurring maintenance fee/month
  • Financial fraud services: Credit Cards, Bank Accounts, Transfers, ATM Deposits
  • CPanel, Shells, SMS Mailers, RDP, Webmail, SSH


The following is an overview of how they operate.

  1. SAIGA sells access to saiga-hub and the related functionality and tools used in the phishing campaigns.
  2. SAIGA configures and sets up the phishing domain and services.
  3. Once the infrastructure has been configured, the phishing domain can be added in the various templates to be used by the SAIGA Mailer.
  4. Updates and logging is provided in both the phishing dashboard, as well as in Telegram.
  5. Upon a successful phishing visit where a victim enters in their credentials, the entire interaction is proxied through to the real Microsoft site (as described in the previous section).
  6. Once that process is complete, both the credentials and cookies are sent to the telegram channel.
  7. After obtaining access to the accounts, the other tools offered by SAIGA are then utilised for further attacks. For example, extracting all email communications (FM Scanner), the emails obtained are then used to carry out future phishing attacks.


As SAIGA simply provides the various phishing services, it is entirely up to the threat actor that has obtained the credentials as to how they proceed. Some might choose to take their time (several months) and carry out a more targeted attack to other employees once they gather more information, whereas others may choose to send additional phishing emails relatively quickly.  The successful logins can also be added to the pool of their SMTP mailers.

As of March 2025, there are currently 123 known domains related to these phishing campaigns, with at least 70 unique active bots. Based on the details obtained from the phishing config, there could be up to 88 users utilising this phishing service, made up of at least 90 domain names. However, this number could potentially be much higher as multiple domains could be using the same configuration, rather than a unique config per domain.

At the core, the backend infrastructure is based upon evilginx with a custom implementation for telegram notifications. This particular evilginx implementation appears to be based upon a upon fpages, it is unclear if SAIGA had purchased this, a spin off group or if the code was simply stolen and built upon.

On each phishing domain the title is randomised based on snippets from Lorem Ipsum to evade detection. There are also similarities between this SAIGA phish-kit, and the Rockstar 2FA phish-kit. The similarities between these can be found within the “attach,loading.htm” file, with the SAIGA version incorporating fitness class names and comments. It is currently unknown if it’s a new version, or if SAIGA has just created their version based upon it. However, they are still vastly different implementations as this SAIGA version appears to be using NodeJS with the Next.js framework.

Figure 9: SAIGA Phishing Page Dashboard


How Red Piranha Found SAIGA?

The initial investigation of the domain used in the phishing campaign against one of our clients quickly enabled us to discover additional domains that have been used, as well as monitor whenever additional sites have been added. This is mostly due to the fact of there being mostly static files used within this phishing-kit.

After searching various online platforms (urlscan.io, shodan, etc) and additional OSINT, we were able to discover many active sites which are used in this phishing campaign.

Each phishing site has various API endpoints that were mentioned earlier in this report. The first API endpoint that came to our attention was the /api/config/ endpoint as this returned information about the domain as well as the telegram chats and bot tokens.

By utilising the telegram API, along with the bot tokens, we were able to scrape the information of each active bot which resulted in obtaining information about the usernames that had been communicating with the bot.  In total, we were able to discover 70 bots and 64 usernames, the bots are essentially where all the logs from the phishing campaigns are sent to.

After scraping all this information, we noticed several usernames and bots that had references to “SAIGA”.  One of the usernames that we investigated was Trailblazer_io,  we discovered a TikTok account under the name, and in the profile picture was an image of the SAIGA log output. There was also a telegram channel linked in the profile description.

After creating a telegram account, we joined that telegram channel and started to scrape all the information we could find. Not only did we discover a large quantity of financial crime being done within that channel, but we also found many advertisements for SAIGA related services.

The next step we took was to scrape data relating to the bots and the chats they were apart of in the hopes of discovering any victims of this phishing campaign so they can be informed. There was only a handful of bots that we were able to find information from due to the others using message expiry timers. But luckily for us, thanks to their apparent opsec failures, we were able to scrape thousands of messages.

After extracting the relevant information, we were able to extract over 8k credentials that had been captured. We were also able to extract at least 175 unique IP addresses that had been used to access the phishing dashboards.

Currently, we are unable to attribute this group to a specific country or a previous group, however, there are several indicators that some of the core members are based out of Nigeria. This can be inferred based on the communication within the telegram channels, as well as the IP addresses that accessed the phishing dashboard.

We are currently in the process of contacting the organisations and affected accounts.

Recommendations and Mitigation

As these more advanced phishing campaigns continue to improve and develop over time, it's important to understand that traditional MFA implementations may no longer be as effective against these types of attacks.

By implementing the following strategies, you can reduce the likelihood of these attacks being carried out against your organisation.

  • Configure Conditional Access Policies
    • Require location or device-based policies. This can ensure that the account can only be accessed from a specific location or device that has been approved
    • Enforce stronger phishing resistant authentication methods (FIDO2 passkeys, certificate-based authentication, Windows Hello)
  • Continuously monitor account logs and active sessions
  • Deploy Secure Web Gateway and a Strong TDIR program to detect multistage attacks.
  • Regularly undergo Security Awareness and Training for employees. This will ensure everyone in the organisation stays up to date with the latest information. With the increase of AI being used in phishing campaigns, identifying suspicious emails will become more difficult.


The IOCs that were discovered throughout this investigation have been added to our threat intelligence platform and pushed to all Red Piranha Crystal Eye devices. Crystal Eye’s Automated Actionable Intelligence keeps a reputation list of bad IPs that is updated on a pre-scheduled basis.

New IPs found from threat intelligence are loaded by the system and are then blocked through the Intrusion Protection System and the Intrusion Detection System. Malicious domains on the other hand are inaccessible due to Crystal Eye’s DNS Sinkholing feature. Crystal Eye also comes with anti-phishing features such as scanning to ensure cryptographic certificates are valid and match the host and detecting links that are cloaked to deceive users. 

Campaign Statistics

Statistic
Statistic Type
Count
Phishing Dashboard Access
Unique IPs
175
Captured Credentials
User/Password
8096
Captured Credentials
Cookies
1397
Telegram Channel (@trailblazer_io)
Subscribers
1210
TikTok Page (@trailblazer_io)
Followers
1215
Telegram Channel (@saiga_hub
Subscribers
792
Estimated Phishing Domains
Domain Count
123
Estimated Phishing Users
User Count
88
Telegram Phishing Bots
Bot Count
70
Telegram Usernames
Username Count
64


SAIGA Infrastructure

Information
Category
Description
saiga-hub.ru
Domain
SAIGA Domain
saiga-hub.com
Domain
SAIGA Domain
saiga-hub-api.com
Domain
SAIGA Domain
saiga-store-hub.com
Domain
SAIGA Domain
saiga-hub.app
Domain
SAIGA Domain
87tvdx.ru
Domain
SAIGA Domain
github.com/SAIGASAIGASAIGA/SAIGA
Repo
SAIGA Git Repo
gitea.com/SAIGA_Group/SAIGA-HUB
Repo
SAIGA Git Repo (Installer)
SAIGA_Group:e2c95ea411d7260ff83a3368a169bd7
[email protected]/SAIGA_Group/SAIGA.git
Repo
SAIGA Git Repo (SAIGA Mailer)
https://gitlab.com/SAIGA-Groups/spage
Repo
SAIGA Phishlet Repo
https://gitlab.com/test3042434/phishlets.git
Repo
SAIGA Phishlet Repo
https://github.com/SAIGA-Groups
Repo
SAIGA Repo
Email
Registered saiga-store-hub.com
https://gitlab.com/safewords1/fpages
Repo
fpages


Detailed TTPs

Tactic
TPP ID
Technique
Reconnaissance
T1591
Gather Victim Org Information
T1598
Phishing for Information
T1598.002
Spearphishing Attachment
T1598.003
Spearphishing Link
T1592
Gather Victim Host Information
T1590.005
Gather Victim Network Information – IP Addresses
T1589
Gather Victim Identity Information
T1589.001
Credentials
T1589.002
Email Addresses
T1589.003
Employee Names
Resource Development
T1583
Acquire Infrastructure
T1583.001
Domains
T1583.003
Virtual Private Servers
T1586.002
Compromise Email Accounts
T1608.005
Stage Capabilities – Link Target
Initial Access
T1566
Phishing
T1566.001
Spearphishing Attachment
T1566.002
Spearphishing Link
Execution
T1204.001
User Execution – Malicious Link
T1204.002
User Execution – Malicious File
Persistence
T1078.004
Valid Accounts – Cloud Accounts
Privilege Escalation
T1078.004
Valid Accounts – Cloud Accounts
Defence Evasion
T1656
Impersonation
T1027
Obfuscated Files or Information
T1027.013
Encrypted/Encoded File
T1550.004
Use Alternate Authentication Material – Web Session Cookie
T1036
Masquerading
Credential Access
T1557
Adversary-in-the-Middle
T1111
Multi-Factor Authentication Interception
T1539
Steal Web Session Cookie
Discovery
T1087.003
Account Discovery – Email Account
T1622
Debugger Evasion
Lateral Movement
T1534
Internal Spearphishing
Collection
T1114.002
Email Collection – Remote Email Collection
Command-and-Control
T1071.001
Application Layer Protocol – Web Protocol
T1568.002
Dynamic Resolution – Domain Generation Algorithms
Exfiltration
T1041
Exfiltration Over C2 Channel
T1567
Exfiltration Over Web Service
Impact
T1657
Financial Theft


IOCs

Indicator
Indicator Type
Description
tr6fvvrdyutgb[.]ru
Domain
Phishing Domain
dswwindsor[.]uk
Domain
Phishing Domain
srv670362[.]hstgr[.]cloud
Domain
Phishing Domain
tftfrtf3tl3drrs3[.]net
Domain
Phishing Domain
trtghhtttf98f3rrtyrs3[.]net
Domain
Phishing Domain
tftfrydrrs3[.]net
Domain
Phishing Domain
wittrams[.]com
Domain
Phishing Domain
support-secureaccess889[.]com
Domain
Phishing Domain
gratisgamez[.]com
Domain
Phishing Domain
hbmarchitects[.]us
Domain
Phishing Domain
authx86[.]name
Domain
Phishing Domain
gllhsco[.]com
Domain
Phishing Domain
sdsd[.]tftfrtf34f3drrs3[.]net
Domain
Phishing Domain
ygialz[.]dns[.]army
Domain
Phishing Domain
maple-view3737262648372847live[.]com
Domain
Phishing Domain
scrumbert[.]org
Domain
Phishing Domain
fourpolntscharleston[.]com
Domain
Phishing Domain
mekanjet[.]com
Domain
Phishing Domain
msgsky[.]net
Domain
Phishing Domain
krustyykozggr[.]com
Domain
Phishing Domain
haasfrance[.]xyz
Domain
Phishing Domain
suporter46sec[.]com
Domain
Phishing Domain
1nterplast-uae[.]com
Domain
Phishing Domain
legacy-tltie[.]com
Domain
Phishing Domain
fillerbred[.]com
Domain
Phishing Domain
accinolabs[.]com
Domain
Phishing Domain
lucastlitonresidential[.]com
Domain
Phishing Domain
tax-secureacess-hrmcmember-sevirce[.]org
Domain
Phishing Domain
Jkeyyyjkjkyy[.]net
Domain
Phishing Domain
commercialrealestatepasadena[.]com
Domain
Phishing Domain
openedss[.]com
Domain
Phishing Domain
fgsftourccytitvcom
Domain
Phishing Domain
southernpipaline[.]org
Domain
Phishing Domain
ganiasoftware[.]com
Domain
Phishing Domain
sdspprfd-tftfrtrghf34f3drrs3[.]net
Domain
Phishing Domain
avarateechnologies[.]com
Domain
Phishing Domain
qssfwiopgte[.]net
Domain
Phishing Domain
docviewsc[.]info
Domain
Phishing Domain
appauthservice[.]online
Domain
Phishing Domain
deskschoolpro[.]com
Domain
Phishing Domain
canvvapro[.]com
Domain
Phishing Domain
yydsedgw[.]icu
Domain
Phishing Domain
libertysteelbulidings[.]com
Domain
Phishing Domain
claudiuspeter[.]com
Domain
Phishing Domain
tysghetagy[.]com
Domain
Phishing Domain
tilcon-lnc[.]com
Domain
Phishing Domain
coxuongkhopbariavungtau[.]com
Domain
Phishing Domain
funantong[.]com
Domain
Phishing Domain
t82pdf[.]com
Domain
Phishing Domain
tilleydistributions[.]com
Domain
Phishing Domain
sharedfdfile[.]net
Domain
Phishing Domain
rostoavc[.]store
Domain
Phishing Domain
brighfordxxtiie[.]com
Domain
Phishing Domain
athena-securlty[.]com
Domain
Phishing Domain
topsuport[.]nl
Domain
Phishing Domain
carolinacraetions[.]biz
Domain
Phishing Domain
offericegoldxcvds[.]com
Domain
Phishing Domain
joysowl[.]life
Domain
Phishing Domain
waternarkinsights[.]com
Domain
Phishing Domain
securesupport1[.]com
Domain
Phishing Domain
shareddocumentso365collaborations[.]com
Domain
Phishing Domain
bassacredith[.]net
Domain
Phishing Domain
exprealtty[.]net
Domain
Phishing Domain
transformersrelationship[.]net
Domain
Phishing Domain
teclhnoform[.]com
Domain
Phishing Domain
fujiitatechnotrade[.]com
Domain
Phishing Domain
quorx[.]net
Domain
Phishing Domain
gdrririgs[.]com
Domain
Phishing Domain
steyr-automotlve[.]com
Domain
Phishing Domain
Invs0[.]online
Domain
Phishing Domain
kfgeyrg[.]net
Domain
Phishing Domain
calmpresidentcould[.]online
Domain
Phishing Domain
secure-autorizacion[.]org
Domain
Phishing Domain
libertylead[.]ru
Domain
Phishing Domain
greatwaters[.]us
Domain
Phishing Domain
vomonllne[.]com
Domain
Phishing Domain
metromechs[.]us
Domain
Phishing Domain
leanmayland[.]com
Domain
Phishing Domain
gm2edv[.]us
Domain
Phishing Domain
blackmiklagency[.]com
Domain
Phishing Domain
constellationlogistics[.]online
Domain
Phishing Domain
eaglebuilders[.]org
Domain
Phishing Domain
fdx-14e[.]ru
Domain
Phishing Domain
amgcareconsultants[.]com
Domain
Phishing Domain
truenortherlocation[.]com
Domain
Phishing Domain
stahlwile-americas[.]com
Domain
Phishing Domain
not-a-robot[.]org
Domain
Phishing Domain
davidbrunelelaw[.]com
Domain
Phishing Domain
doginme[.]tech
Domain
Phishing Domain
integritytankservices[.]online
Domain
Phishing Domain
gunbycos[.]com
Domain
Phishing Domain
anplife[.]us
Domain
Phishing Domain
secure-autotransltd[.]com
Domain
Phishing Domain
flymerlnaerospace[.]com
Domain
Phishing Domain
588mj[.]com
Domain
Phishing Domain
modermice[.]com
Domain
Phishing Domain
securemailmethological[.]com
Domain
Phishing Domain
borderrstates[.]com
Domain
Phishing Domain
boninevilliebuillders[.]xyz
Domain
Phishing Domain
ladingcargos[.]com
Domain
Phishing Domain
natlonalfoodgroup[.]com
Domain
Phishing Domain
sharedflz[.]xyz
Domain
Phishing Domain
conitractcare[.]net
Domain
Phishing Domain
boninevilliebuillders[.]info
Domain
Phishing Domain
hbezecdc[.]com
Domain
Phishing Domain
tb0[.]online
Domain
Phishing Domain
saettleboat[.]com
Domain
Phishing Domain
theontimeexpert[.]com
Domain
Phishing Domain
paanilani[.]biz
Domain
Phishing Domain
secure-autoscout[.]org
Domain
Phishing Domain
lauzdhstk[.]com
Domain
Phishing Domain
ntxnano[.]com
Domain
Phishing Domain
flzsndzf[.]top
Domain
Phishing Domain
faxonlineringdoc[.]info
Domain
Phishing Domain
https://sites[.]google[.]com/cumlc.com/adkjsks/home
URL
Phishing Website
145.223.97[.]151
IP
Infrastructure
145.223.100[.]114
IP
Infrastructure
192.3.255[.]173
IP
Infrastructure
172.245.92[.]207
IP
Infrastructure
107.174.244[.]119
IP
Infrastructure
217.15.175[.]147
IP
Infrastructure
172.245.21[.]204
IP
Infrastructure
192.3.255[.]147
IP
Infrastructure
194.5.212[.]74
IP
Infrastructure
172.245.21[.]214
IP
Infrastructure
185.211.101[.]82
IP
Infrastructure
177.136.225[.]221
IP
Infrastructure
107.173.160[.]169
IP
Infrastructure
130.195.222[.]216
IP
Infrastructure
185.212.44[.]34
IP
Infrastructure
23.227.199[.]88
IP
Infrastructure
192.3.255[.]146
IP
Infrastructure
147.45.49[.]157
IP
Infrastructure
23.227.199[.]36
IP
Infrastructure
37.221.114[.]33
IP
Infrastructure
79.110.52[.]25
IP
Infrastructure
145.223.81[.]147
IP
Infrastructure
82.29.178[.]105
IP
Infrastructure
147.93.62[.]145
IP
Infrastructure
194.5.212[.]245
IP
Infrastructure
172.245.21[.]219
IP
Infrastructure
172.245.21[.]212
IP
Infrastructure
86.38.203[.]246
IP
Infrastructure
192.3.255[.]188
IP
Infrastructure
146.70.88[.]75
IP
Infrastructure
173.195.100[.]50
IP
Infrastructure
146.70.87[.]43
IP
Infrastructure
193.27.14[.]204
IP
Infrastructure
192.3.255[.]174
IP
Infrastructure
146.70.92[.]163
IP
Infrastructure
107.174.244[.]111
IP
Infrastructure
23.94.126[.]14
IP
Infrastructure
147.93.122[.]224
IP
Infrastructure
192.3.255[.]183
IP
Infrastructure
51.77.121[.]150
IP
Infrastructure
166.88.185[.]43
IP
Infrastructure
89.44.9[.]193
IP
Infrastructure
206.189.24[.]120
IP
Infrastructure
23.26.201[.]210
IP
Infrastructure
89.45.4[.]77
IP
Infrastructure
5.181.3[.]13
IP
Infrastructure
51.38.106[.]85
IP
Infrastructure
194.5.212[.]135
IP
Infrastructure
24.199.110[.]25
IP
Infrastructure
162.19.196[.]8
IP
Infrastructure
162.244.210[.]60
IP
Infrastructure
162.244.210[.]224
IP
Infrastructure
198.23.221[.]11
IP
Infrastructure
151.242.58[.]168
IP
Infrastructure
23.26.108[.]201
IP
Infrastructure
23.26.108[.]160
IP
Infrastructure
104.234.114[.]37
IP
Infrastructure
151.242.58[.]189
IP
Infrastructure
37.120.222[.]185
IP
Infrastructure
46.202.155[.]217
IP
Infrastructure
46.101.165[.]24
IP
Infrastructure
31.58.169[.]63
IP
Infrastructure
31.196.71[.]6
IP
Infrastructure
65.52.217[.]35
IP
Infrastructure
147.79.104[.]170
IP
Infrastructure
45.61.133[.]34
IP
Infrastructure
198.12.118[.]212
IP
Infrastructure
638684131a3ad09b62d819e5f0113a3e04d7e2fb81337
54a6648bcab12cc08e0
Hash (SHA-256)
/attach,loading.htm
4be8c3fc908c73bf3731d327f64591373416a7407d819
9e4cfc4ea5267ede5db
Hash (SHA-256)
/attach,loading.htm
ba42a91b2f5eb8c87ce8a4c7eebe021bb73dc4e6c66c3
afe597a9e739208bed7
Hash (SHA-256)
/microsoft.jpg
12b9f1449fadfdd9be3e4ad5f49e4e2f50ef9f3a169f745
01cf771cf32153329
Hash (SHA-256)
/key.jpg
9a2f494181dcb5f7a5db72bbd94d63510330d53e8e85
fc5b8c5d87a6d4fdd7bc
Hash (SHA-256)
/favicon.ico
dea8ca51e76f7ed7f2a2008bbf532db6ffb07a5bc417e7
b80169d08179810b41
Hash (SHA-256)
webpack-20efd41c90b5bcbd.js
ce7e744b8bd4514883245410370df5e67e4be128d94d
010989b53ecfbf97ef9a
Hash (SHA-256)
23-5e92960ee97bfa6f.js
72def9a0948600afb1dc84350b7c60975b7cd713ac6e9
2647308971fdad8a994
Hash (SHA-256)
main-app-6e9565c54018939e.js


Does detecting malicious activity pose a significant challenge for your organisation?

Red Piranha’s Crystal Eye, best-in-class Threat Detection, Investigation and Response (TDIR), allows you to catch what the other products in its class missed by detecting all known malware and C2 callouts.

Improve your organisation's security posture and minimise risk to your organisation with our Network Detection and Response program alongside the Managed Detection and Response (MDR) service.

-- New Update on 21/3/2025

Looks like they've read our blog. 

Many of the domains no longer resolve to any IPs. The ones that don't appear to have any connection to the backend infrastructure (/api/config returns an error message similar to "error: site not found"). Their API server is also down, which is likely causing the error.

Gitea accounts/repos have been deleted.
​​​​​​​
The Telegram channel (https://telemetr.io/en/channels/1961642115-GSS8UceztVZhYzk0/publish) has been renamed and set to private.

The TikTok account has been deleted as well.



Details
Category
Last Updated
March 21, 2025