Rankiteo Logo
Rankiteo
Leader in Cyber Underwriting
Loading...
NEWRankiteo Cyber Underwriting Desktop - Score, price, and bind from your desktop
WindowsmacOSLinux
Download
ANY.RUN

ANY.RUN Vendor Cyber Rating & Cyber Score

any.run

ANY.RUN is built to help security teams detect threats faster and respond with greater confidence. Our goal is to help organizations boost investigation of cybersecurity incidents and increase skill levels of analysts — all while saving resources and time. ANY.RUN's Interactive Sandbox delivers real-time malware analysis and threat intelligence, giving analysts the clarity they need when it matters most. With support for Windows, Linux, and Android environments, our cloud-based sandbox enables deep behavioral analysis without the need for complex setup. Paired with Threat Intelligence Lookup and Feeds, ANY.RUN provides rich context, actionable IOCs, and automation-ready outputs, all with zero infrastructure burden. Follow us on X,


ANY.RUN A.I CyberSecurity Scoring

ANY.RUN
Company Information
Website:https://any.run/?utm_source=linkedin&utm_campaign=bio
Employees number:375
Number of followers:22,119
NAICS:541514
Industry Type:Computer and Network Security
Homepage:any.run
ANY.RUN Risk Score (AI oriented)
Between 600 and 649
logo
ANY.RUNComputer and Network Security
Updated:
08/07/2026
633/1000
Poor
Caa
AaaAaABaaBaBCaaCaC
Powered by our proprietary A.I cyber incident model
Insurance prefers TPRM score to calculate premium
ANY.RUN Global Score (TPRM)
xxxx
logo
ANY.RUNComputer and Network Security
•••
Score locked
Instant access to detailed risk factors
Vulnerabilities
Benchmark vs. industry & size peers
Findings

ANY.RUN
ANY.RUNPoor
Current Score
633Caa (POOR)
01000
2 incidents
-65 avg impact
Incident timeline with MITRE ATT&CK tactics, techniques, and mitigations.
AUGUST 2026
636Before Incident
JULY 2026
633Before Incident
JUNE 2026
632Before Incident
MAY 2026
650Before Incident
Cyber Attack
25 May 2026ANY.RUN
Banana RAT: Banana RAT Uses Exposed Payload Generator to Create Polymorphic Banking Malware Variants

Banana RAT Campaign Exposed: Malware Builder Generates Fresh Variants on Demand

630After Incident
CRITICAL-20
ANY1783528011
Banana RAT Campaign Exposed: Malware Builder Generates Fresh Variants on Demand A recent discovery by researcher Moises Cerqueira has uncovered a sophisticated upgrade to Banana RAT, a remote access trojan (RAT) linked to Brazilian banking fraud. The malware’s operators are now using an exposed backend server to dynamically generate new, obfuscated variants in real time, evading traditional detection methods. The exposed server, hosted at 198.245.53.26, functioned as a payload generator, running scripts like servidor_completo_pool.py to produce fresh malware batches. A secondary script, ofuscador.py, scrambled PowerShell commands into randomized sequences, ensuring each payload appeared unique while maintaining core malicious functionality. ### Key Findings from the Campaign - Two Distinct Versions Detected: Researchers at ANY.RUN analyzed two Banana RAT variants one from late May 2026 and another from early June 2026 both originating from the same infrastructure. - May Version: Used fixed file paths and a misspelled domain (c.windowns-cdn.com) to mimic legitimate Windows updates. Persistence relied on a scheduled task tied to a named executable (MicrosoftEdgeUpdateCore.exe). - June Version: Adopted randomized file names and folders, a VBS launcher, and system-level scheduled tasks for persistence. Communication shifted to encrypted WebSocket channels with hashed, machine-specific subdomains (testewin.com), complicating domain-based blocking. - Shared Infrastructure: Both versions retained a fallback C2 IP (149.56.12.51), linking them to the same operation. The newer variant also resolved to Cloudflare edge IPs (104.21.39.172, 67.142.55) for command-and-control (C2) traffic. ### Impact on Defenders Banana RAT’s on-demand regeneration undermines blocklist-based defenses, as each infection appears distinct. The exposed server provided defenders with a rare, real-time view of malware evolution, offering insights into how attackers refine evasion techniques. The trojan’s primary focus remains stealing banking credentials and hijacking payment transactions, posing a direct threat to financial institutions and users. ### Indicators of Compromise (IoCs) Security teams are advised to monitor for: - IPs: `198.245.53.26` (staging server), `149.56.12.51` (fallback C2), `104.21.39.172`/`67.142.55` (Cloudflare C2). - Domains: `c.windowns-cdn.com` (older), `testewin.com` and subdomains (newer). - Files: `Fatura-BtgPactual-22568.bat`, `msedgeupdate.txt`, `st.php.malw`, `payload_new.php.malw`, `c9dba5b0552d879be654.txt`, and `MicrosoftEdgeUpdateCore.exe`. The discovery highlights the growing sophistication of banking malware, where automated payload generation enables rapid adaptation to defensive measures.
INCIDENT DETAILS -
TYPE
Malware (RAT)
MOTIVATION
Financial gain (banking fraud, credential theft, payment hijacking)
IMPACT
Data Compromised: Banking credentials, payment transaction dataSystems Affected: Windows systems (via malicious executables and scheduled tasks)Operational Impact: Potential unauthorized access to financial systems, transaction hijackingIdentity Theft Risk: High (PII and financial data theft)Payment Information Risk: High (payment transaction hijacking)
DATA BREACH
Type Of Data Compromised: Banking credentials, payment transaction data, personally identifiable information (PII)Sensitivity Of Data: High (financial and PII data).bat.txt.php.malw.exePersonally Identifiable Information: Yes (banking credentials, transaction data)
APRIL 2026
649Before Incident
MARCH 2026
647Before Incident
FEBRUARY 2026
753Before Incident
Ransomware
11 Feb 2026ANY.RUN
ANY.RUN: BQTLock & GREENBLOOD Ransomware Attacking Organizations to Encrypt and Exfiltrate Data

Emergence of BQTLock and GREENBLOOD Ransomware Strains

643After Incident
MEDIUM-110
ANY1770832431
New Ransomware Strains BQTLock and GREENBLOOD Showcase Evolving Threat Tactics Two advanced ransomware families, BQTLock and GREENBLOOD, have emerged with distinct strategies, complicating detection and response for cybersecurity teams. BQTLock operates as a stealthy espionage tool, embedding itself within legitimate system processes such as explorer.exe to evade detection. Using a Remcos payload, it bypasses traditional antivirus by masquerading as trusted Windows activity. The malware then executes a UAC bypass via *fodhelper.exe*, gaining elevated privileges without user interaction. Once persistent, it harvests credentials and screenshots, delaying encryption to maximize data theft before extortion. In contrast, GREENBLOOD prioritizes speed, leveraging Go-based ChaCha8 encryption to lock systems within minutes. It employs a "smash-and-grab" approach, deleting forensic evidence and pressuring victims via a TOR-based leak site. Unlike BQTLock’s slow infiltration, GREENBLOOD’s rapid execution leaves little time for intervention. Analysts at ANY.RUN uncovered these behaviors in sandbox environments, where real-time execution chains revealed critical early indicators such as unexpected process injections and rapid file modifications. Detecting these signs before encryption is key to containment, as both strains exploit gaps in traditional signature-based defenses. BQTLock’s persistence mechanisms and GREENBLOOD’s destructive speed highlight the need for behavioral monitoring and updated threat intelligence to counter these evolving threats. Organizations are advised to watch for anomalous interactions between explorer.exe and fodhelper.exe, along with the unique command-line patterns associated with these strains.
INCIDENT DETAILS -
TYPE
Ransomware
MOTIVATION
Data TheftExtortion
IMPACT
Data Compromised: Credentials, Screenshots, Sensitive FilesIdentity Theft Risk: High
DATA BREACH
CredentialsScreenshotsSensitive FilesSensitivity Of Data: HighData Exfiltration: YesData Encryption: Yes (ChaCha8 for GREENBLOOD)
JANUARY 2026
753Before Incident
DECEMBER 2025
753Before Incident
NOVEMBER 2025
753Before Incident
OCTOBER 2025
753Before Incident
SEPTEMBER 2025
753Before Incident

Frequently Asked Questions

?
What is the current A.I Rankiteo Cyber Score for ANY.RUN ?
?
What was ANY.RUN's A.I Rankiteo Cyber Score in July 2026 ?
?
What was ANY.RUN's A.I Rankiteo Cyber Score in June 2026 ?
?
What was ANY.RUN's A.I Rankiteo Cyber Score in May 2026 ?
?
What was ANY.RUN's A.I Rankiteo Cyber Score in April 2026 ?
?
What was ANY.RUN's A.I Rankiteo Cyber Score in March 2026 ?
?
What was ANY.RUN's A.I Rankiteo Cyber Score in February 2026 ?
?
What was ANY.RUN's A.I Rankiteo Cyber Score in January 2026 ?
?
What was ANY.RUN's A.I Rankiteo Cyber Score in December 2025 ?
?
What was ANY.RUN's A.I Rankiteo Cyber Score in November 2025 ?
?
What was ANY.RUN's A.I Rankiteo Cyber Score in October 2025 ?
?
What was ANY.RUN's A.I Rankiteo Cyber Score in September 2025 ?
?
What is the average per-incident point impact on ANY.RUN's A.I Rankiteo Cyber Score over the past 12 months ?
?
Where can I access detailed records of all cyber incidents associated with ANY.RUN ?
?
Where can I find a summary of the A.I Rankiteo Risk Scoring methodology ?
?
Where can I view ANY.RUN's profile page on Rankiteo ?
?
How accurate is the A.I Rankiteo Risk Scoring methodology ?
ANY.RUN Cyber Scoring History | Rankiteo