Skip to content
Full Tech ZeroDayRat ₿ 0.10 BTC

Entity Reference

What Is ZeroDayRAT?

A structured, evidence-classified introduction to ZeroDayRAT — what public research establishes, what sellers claim, and what remains unverified.

ReportedLast reviewed: 2026-08-31By Daniel Voss, Lead Threat Researcher

Quick Answer

What is ZeroDayRAT?

ZeroDayRAT is the name used for a commercially marketed mobile surveillance and remote-access platform documented by security researchers in 2026. Reported capabilities include device profiling, location monitoring, SMS and notification access, camera and microphone surveillance, screen monitoring, keylogging and financial targeting. Public evidence does not currently establish that the platform necessarily relies on a genuine zero-day or zero-click exploit.

Executive Summary

  • ZeroDayRAT is a commercially marketed mobile spyware / remote-access platform, publicly documented from February 2026.
  • Reported functionality spans device profiling, location, SMS, notifications, camera, microphone, screen, input capture and financial targeting.
  • No public evidence establishes a genuine ZeroDayRAT zero-day exploit or a demonstrated zero-click infection chain.
  • The strategic significance is commoditization: surveillance capability packaged behind an operator console.
  • Defensive posture should assume identity compromise follows device compromise.

Capability-to-Permission Mapping

Press coverage lists what ZeroDayRAT can reportedly do. The table below goes further: it maps each reported capability to the specific Android permission or API surface it would require, and to the iOS platform constraint that limits or prevents it. For defenders, this is the bridge between a threat report and an actionable MDM policy or permission audit. If your fleet enforces the Android permissions in the right-hand column, the corresponding capability is materially harder to exercise regardless of which operator deploys the tool.

Reported CapabilityAndroid Permission / API SurfaceiOS ConstraintEvidence
Device profilingREAD_PHONE_STATE, package queriesLimited — sandboxed; device model via public APIReported
Location trackingACCESS_FINE_LOCATION, background locationAlways-Use location authorization (prompted)Reported
SMS & OTP interceptionRECEIVE_SMS, READ_SMS, SMS Retransmission APINo direct SMS access; interception via notification or clipboardReported
Notification accessNotificationListenerService (BIND_NOTIFICATION_LISTENER)Notification content not directly accessible to third-party appsReported
Camera surveillanceCAMERA, foreground service (background capture)Camera indicator mandatory; background capture constrainedReported
Microphone surveillanceRECORD_AUDIO, foreground serviceMicrophone indicator mandatory; background recording constrainedReported
Screen monitoringMediaProjection API (user consent prompt per session)Screen Recording Broadcast extension (per-session prompt)Reported
Keylogging / input captureAccessibility Service (BIND_ACCESSIBILITY_SERVICE)No system-wide keylogging; custom keyboard injection onlyAdvertised / Claimed
Clipboard manipulationClipboard manager access (background, API-dependent)Clipboard access restricted from iOS 14+ (banner notification)Reported
Financial targeting (banking)Overlay attacks (SYSTEM_ALERT_WINDOW), accessibilityNo system-wide overlay; phishing via fake app icons onlyAdvertised / Claimed
Remote command executionForeground service, network socket, WorkManagerBackground networking limited; VoIP push for wakeReported
Persistence / auto-startRECEIVE_BOOT_COMPLETED, accessibility (self-restart)No background daemon model; requires exploit or MDM profileUnconfirmed

Original Analysis

This mapping is an original analytical product of the ZeroDayRAT Intelligence Center. It is not reproduced from iVerify, ThaiCERT, or press reporting. It exists to convert reported capabilities into concrete permission-policy actions that security teams can implement today.

Evidence Confidence Matrix

Not every reported ZeroDayRAT capability rests on the same quality of evidence. Some have been independently observed by researchers; others appear only in operator-facing marketing material. The matrix below separates what is observed from what is claimed, so defenders can calibrate investment — spending on exploit-mitigation for an unconfirmed zero-day claim is very different from spending on permission controls for a reported capability.

Claim or CapabilityEvidence BasisStatusAnalytical Note
Commercial availability with operator dashboardMarketing material + researcher observationReportedMultiple screenshots of management interface independently surfaced
Android device profiling and location collectionResearcher analysis of reported functionalityReportedConsistent with standard Android permission model
SMS / OTP interception on AndroidReported capability + platform feasibilityReportedAndroid SMS permissions enable this; iOS does not
Camera and microphone surveillanceAdvertised in operator materialAdvertised / ClaimedNo independently published sample demonstrating capture
Screen monitoring and keyloggingOperator-facing marketingAdvertised / ClaimedAndroid accessibility service is the likely vector; iOS infeasible without exploit
Financial targeting (banking / crypto)Advertised capability setAdvertised / ClaimedOverlay + accessibility on Android; limited on iOS
iOS full-spectrum surveillanceSeller compatibility claimsUnconfirmedNo independent technical validation on real iOS devices
Genuine zero-day exploit chainInterface label referencing "exploit"UnconfirmedA label is a claim, not a demonstrated vulnerability
Zero-click installationImplied by product name; not demonstratedUnconfirmedNo public evidence of zero-click delivery; user-involved installation reported
Cross-platform persistence without MDMInferred from capability marketingUnconfirmediOS persistence without exploit or MDM profile is not established

How to Use This Matrix

Treat Reported items as the planning baseline for detection and policy. Treat Advertised items as plausible but unverified — monitor for indicators without assuming deployment. Treat Unconfirmed items as risk to watch, not fact to build against.

Where ZeroDayRAT Sits: The Spyware Commoditization Spectrum

ZeroDayRAT is often described as “spyware,” but that label alone does not tell defenders where to invest. The proprietary model below positions commercial mobile surveillance tools on a spectrum from bespoke nation-state implants to consumer stalkerware, scored by operator barrier, detection posture, and infrastructure model. ZeroDayRAT occupies Tier 2 — commoditized malware-as-a-service — which is precisely why the standard Pegasus playbook (specialized hunting, government disclosure, advanced mobile threat detection) does not transfer. Tier 2 threats are defeated by permission governance, MDM policy, and behavioral correlation, not by exploit-mitigation tooling.

TierCategoryExamplesOperator BarrierDetection PosturePosition
Tier 0Bespoke / Nation-StatePegasus, Predator (mercenary spyware)Extremely high — custom exploit chains, dedicated infrastructureRequires advanced mobile threat detection (MTD), forensic analysisNot ZeroDayRAT
Tier 1Commercial MercenaryFinFisher, Cytrox-era productsHigh — six-to-seven-figure licensing, vetted buyersTargeted hunting, specialized IOCs, government disclosureNot ZeroDayRAT
Tier 2Commoditized MaaSZeroDayRAT (reported)Low-to-moderate — dashboard, documentation, support channelsPermission auditing, behavioral correlation, MDM policy enforcement← ZeroDayRAT
Tier 3Consumer StalkerwareCommercial "monitoring" apps (app-store-adjacent)Very low — consumer pricing, app-store or sideload distributionMDM blocklists, app-store review, user educationNot ZeroDayRAT

Original Framework

The Spyware Commoditization Spectrum is an original framework developed by the ZeroDayRAT Intelligence Center. It reframes the threat not by capability set (which is similar across tiers) but by operator accessibility — the variable that most directly determines how many distinct infrastructure clusters a defender will face and how quickly indicators will churn.

ZeroDayRAT Definition

“ZeroDayRAT is the name used for a commercially marketed mobile remote-access and surveillance platform publicly documented by security researchers in 2026.”

Expanding on that definition: ZeroDayRAT (also written ZerodayRAT or Zero Day RAT) refers to a software offering rather than a single malware sample. Public reporting describes a package consisting of a mobile component that runs on a target device and a management interface through which an operator issues instructions and reviews collected information. This is the classic structure of a remote-access trojan, differentiated mainly by how it is sold and how accessible it is to non-specialist buyers.

The distinction between a “platform” and a “sample” matters for defenders. Because ZeroDayRAT is marketed to multiple buyers, each operator may run separate infrastructure, choose different delivery pretexts and enable different subsets of functionality. Consequently, indicators from one incident may have limited value in another, and detection strategies that depend on a fixed domain list or a single file hash will age badly.

When Was ZeroDayRAT Discovered?

ZeroDayRAT entered public cybersecurity discussion in February 2026. Initial identification and reporting was followed within the same month by broader coverage in established cybersecurity media and CERT-style advisories that summarised the reported capability set and the commercial marketing around it.

Because the public record is recent, the intelligence picture is necessarily incomplete. Some functionality has been described from marketing material and operator-facing interfaces rather than from independent technical validation on real devices. We therefore label each capability with an evidence classification rather than presenting a single flat feature list.

Why Security Researchers Are Paying Attention

The interest in ZeroDayRAT is less about novel exploitation and more about accessibility. Historically, comprehensive mobile surveillance required either bespoke development or the budget to procure a specialist surveillance product. When comparable functionality is packaged with a dashboard, documentation and support channels, the population of people capable of running a mobile surveillance operation grows sharply.

  • Lower technical barrier: operating a console is not the same skill as writing an implant.
  • Wider operator base: fraud actors, harassment actors and opportunistic criminals, not only espionage actors.
  • Fragmented infrastructure: many independent operators, weakening takedown-based mitigation.
  • Faster iteration: a vendor updating one platform propagates changes to every operator at once.

Is ZeroDayRAT Malware?

Yes, under the standard security definition. Software installed on a device without the informed consent of that device’s user, for the purpose of covert collection or remote control, is malware. Commercial packaging, terms of service, or a claim that the product is intended for “monitoring” do not change the technical classification when the deployment is unauthorized.

Join Our Community

ZeroDayRAT Intelligence on Telegram

Get real-time mobile spyware alerts, threat briefings, and defensive guidance.

Join the Channel

Is ZeroDayRAT Spyware?

The reported functionality is surveillance functionality. Location collection, message and notification visibility, camera and microphone access, screen monitoring and input capture all serve the purpose of observing a person rather than damaging or ransoming data. That functional profile is what the term spyware describes, and it is why the appropriate defensive frame is surveillance risk rather than only data-loss risk.

Professional Spy Phones — Zero-Click Spyware for authorized investigative and cyber intelligence operations

Is ZeroDayRAT a RAT?

A remote-access trojan is malware that provides an operator with ongoing remote control of an affected device. Public reporting describes exactly that pattern for ZeroDayRAT: a console from which commands are issued and results retrieved. The presence of remote administration is significant because persistent access is worth more to an attacker than any single act of data theft — collection can be re-tasked as the target’s circumstances change.

Does ZeroDayRAT Use a Zero-Day?

Not publicly confirmed. Public reporting has discussed an “exploit” function visible in material associated with the platform, but independent researchers have not publicly confirmed a genuine ZeroDayRAT zero-day exploit chain. A label inside an operator interface is a claim, not a demonstration.

Evidence Discipline

A product calling itself “ZeroDayRAT” does not prove that it contains an undisclosed zero-day exploit. Treating a marketing name as a technical finding leads defenders to over-invest in exploit mitigation and under-invest in the delivery and permission controls that public evidence actually points to.

Is ZeroDayRAT Zero-Click?

No publicly demonstrated ZeroDayRAT zero-click infection chain should be treated as established fact without independent evidence. Zero-click exploitation is a demanding engineering achievement, typically requiring a reachable parsing surface, memory-safety failure, sandbox escape and reliable delivery. Public ZeroDayRAT reporting has centred on user-involved installation instead.

What Devices Does ZeroDayRAT Target?

Android has been the primary environment in public reporting, which is consistent with the platform’s openness to applications installed outside official distribution channels. iOS targeting has also been reported or advertised. Defenders should hold these two statements apart: claimed compatibility and independently demonstrated compatibility are not necessarily identical, and iOS’s sandboxing, code signing and entitlement model mean that Android techniques do not transfer automatically.

Who Is At Risk?

  • Executives and board members whose devices hold strategic communications.
  • Government officials and public-sector staff.
  • Journalists, researchers and civil-society figures.
  • Cybersecurity personnel, who are attractive as a route into their employer.
  • Finance professionals with payment or treasury authority.
  • Cryptocurrency users, where theft is immediate and irreversible.
  • Corporate employees with mobile access to SSO, email and internal applications.
  • High-value individuals subject to litigation, negotiation or harassment.
  • Ordinary consumers exposed to malicious applications or social engineering.

Why Mobile Spyware Matters to Enterprises

A modern enterprise authenticates people, not offices. A phone typically holds or can approve the factors that gate corporate email, cloud consoles, chat platforms, CRM systems and VPN access. When the endpoint that approves authentication is itself observed, the assurance value of that approval falls sharply.

This is why mobile compromise should be triaged as an identity incident, not only a device incident. Session review, token revocation, MFA-method audit and mailbox-rule inspection are as important as anything done to the handset.

Key Takeaways

  • ZeroDayRAT is a commercially marketed mobile spyware / RAT platform first publicly documented in February 2026.
  • Reported capabilities cover device, location, messaging, notification, media, input and financial surveillance.
  • No public technical evidence establishes a ZeroDayRAT zero-day or a demonstrated zero-click chain.
  • Android is the primary reported environment; iOS targeting is reported or advertised but not independently demonstrated at scale.
  • The most important defensive consequence is identity exposure following endpoint compromise.
  • Detection should correlate device, identity, network and behavioural telemetry rather than rely on static indicators.

Evidence & Sources

ZeroDayRAT reporting summarised here draws on public cybersecurity research and CERT-style reporting from February 2026 onward. We distinguish independently observed technical evidence from media reporting, operator claims and our own analytical assessment. Primary sources are linked so readers can verify claims directly.

Source verification policy: see Editorial Policy

Support This Publisher

Research Standard

We distinguish independently observed technical evidence from media reporting, vendor claims and analytical assessment. Our objective is to document mobile threats accurately without facilitating unauthorized surveillance. This site publishes no exploit code, payloads or deployment instructions.

Evidence Classification Legend

Observed
Directly observed in independent analysis or testing.
Confirmed
Independently verified by multiple sources with technical evidence.
Reported
Reported by credible security researchers but not fully independently verified.
Advertised / Claimed
Claimed by the seller or operator; not independently verified.
Unconfirmed
Cannot be confirmed or denied based on available public evidence.
Analytical Assessment
Analytical conclusion based on reasoning from available evidence.
Contact us on Telegram