Party Panel: Android Banking Trojan Rental Targets India
TL;DR · the short version
On 20 November 2026 CloudSEK published research on a malware-as-a-service operation it calls the "Party" panel. CloudSEK says one unprotected server let paying "tenants" (50 accounts, 34 on paid licences of 7 to 60 days, approved 8 to 12 November) pick an Indian bank or card brand, generate a fake Google Play page and get a branded Android APK. The lure page collects card number, expiry, CVV, date of birth and mother's name keystroke by keystroke; the APK is a dropper that installs a hidden SMS stealer which forwards every SMS (including bank OTPs), uploads the SMS inbox and gallery photos, sends SMS from the victim's number and sets call forwarding so bank verification calls reach the criminal. CloudSEK says six banks and card issuers were targeted, plus government lures (traffic e-challans, a farmer income-support scheme, pensioners' life certificates). It anonymises the institutions, gives no victim count and assesses with medium confidence that the operator is in India. Victim records were referred to the affected institutions, CERT-In and I4C.
On 20 November 2026, CloudSEK published research on a rent-a-trojan service it calls the "Party" panel. CloudSEK says paying "tenants" used it to build fake Google Play pages and branded Android banking malware aimed at customers of six Indian banks and card issuers, and at users of Indian government services such as traffic e-challans. The malware steals card details, intercepts one-time passwords (OTPs) and forwards the bank's verification calls to the criminal. CloudSEK does not name the banks or give a victim count.
Who this is for: fraud and security teams at Indian banks, card issuers and fintechs, mobile security owners, and anyone briefing customers or staff on sideloaded apps.
Independent summary of CloudSEK's report. PlayCISO is not affiliated with CloudSEK. Facts as published on 20 November 2026.
Confirmed vs not yet known
CloudSEK states: one unprotected server hosted the panel, with 50 tenant accounts (34 on paid licences of 7 to 60 days, approved 8 to 12 November 2026); 19 approved tenants went live on 10 November; the panel API answered without a login; six banks and card issuers plus government-service lures were targeted; victim records were referred to the affected institutions, CERT-In and I4C.
CloudSEK assesses (medium confidence): the operator is based in India, from Hinglish page text, Asia/Kolkata timestamps, Indian hosting and all-Indian targets. No real person was identified.
Not stated: the names of the banks and card issuers, how many people were infected or lost money, licence prices, and which channels (SMS, WhatsApp) actually carried the links.
How it works, per CloudSEK
- Tenant sets up a brand. A tenant picks a bank or card brand, a page design (Play Store clone, netbanking portal or bare download page), a card form and its own Telegram bot. The panel builds a branded APK.
- Fake Play Store page. A "<BANK> CREDIT CARD - Apps on Google Play" page copies the store layout, rating, download count and a "Play Protect Verified" badge. It asks for mother's name, date of birth, card number, expiry and CVV, and sends each keystroke to the panel as it is typed. Then it tells the visitor, in Hinglish, to install the APK.
- Dropper. The first app (
com.secure.android.manager) asks for three permissions, then installs a hidden payload while posing as the Play Store, which on Android 13 and later skips Restricted Settings. It also disables the Play Protect verifier. - SMS stealer. The payload (
com.userdb.customer) has no launcher icon, restarts on boot, takes commands through Firebase Cloud Messaging, forwards every SMS to the operator, uploads the inbox and gallery photos, can send SMS from the victim's number, and turns on call forwarding with a USSD code so bank verification calls go to the operator.
CloudSEK's summary: card details plus OTPs plus call forwarding give the operator what is needed for card-not-present fraud.
Useful next, if this was relevant to you
Timeline
| Date (2026) | What | Source |
|---|---|---|
| 8-12 Nov | Paid tenant licences (7 to 60 days) approved on the panel | CloudSEK |
| 10 Nov | 19 of 34 approved tenants go live | CloudSEK |
| 14 Nov | CloudSEK records three bank and card lures with live pages and APKs, others APK only | CloudSEK |
| 20 Nov | CloudSEK publishes the report; records referred to institutions, CERT-In and I4C | CloudSEK |
What to look for
- Package names (CloudSEK): dropper
com.secure.android.manager, payloadcom.userdb.customer. CloudSEK also lists the signing certificate SHA-1927ca44949d7788aa86f9d7f04d7fdacecd1dfb9(CN=editor), used for both stages. - Fraud signals: call forwarding switched on shortly before a card-not-present transaction; OTPs requested from a new device; a customer reporting that the bank "never called back".
- Lure pages: bank-branded "Play Store" pages served from a bare IP on port 8080. CloudSEK shares full indicator values with vetted partners on request; the public values are partly redacted, so take them from CloudSEK.
What security leaders should do this week
- Banks and card issuers: ask the fraud team whether call-forwarding activation and new-device OTP use are joined to card-not-present risk scoring today. If not, that is the gap this kit exploits.
- Publish (or republish) a customer advisory that names your only official app package and says no real Play Store page asks for a card number or CVV.
- Add the two package names and the certificate hash to mobile threat-defence and brand-monitoring rules.
- Tell customer-support teams the recovery script: dial ##002# to cancel call forwarding, block the card, uninstall, report at cybercrime.gov.in or 1930.
- For staff phones under management: block installs from unknown sources, and alert when an app other than the Play Store installs packages.
- Report abuse of hosting, Firebase and Telegram quickly. CloudSEK notes new branded APKs can be built in minutes.
FAQ
What is the Party panel?
It is CloudSEK's name for a malware-as-a-service panel it found on one unprotected server and described on 20 November 2026. Each tenant picks a brand, a page design (a Play Store clone, a netbanking portal or a bare download page), a card-data form and its own Telegram bot, and the panel builds a branded Android APK. CloudSEK counted 50 tenant accounts, 34 of them on paid licences of 7 to 60 days, and says 19 of the approved tenants went live on 10 November 2026.
Which Indian banks are targeted by the Party panel?
CloudSEK does not name them. It says six banks and card issuers were targeted and lists them only as anonymised labels (for example "Bank A (private sector): credit card and limit increase" and "Card issuer B: credit card and pension card"). The government lures it lists are traffic e-challans, a farmer income-support scheme and pensioners' life certificates. If you are a customer, assume any "credit card" or "e-challan" APK sent outside the Play Store is suspect.
What does the malware steal?
According to CloudSEK, the fake Play Store page collects mother's name, date of birth, card number, expiry and CVV, sending each keystroke as it is typed, so even an abandoned form leaks data. The installed payload forwards every incoming SMS (including bank OTPs) to the operator, uploads the SMS inbox and gallery photos (which may include card, Aadhaar and PAN images), can send SMS from the victim's number, and sets call forwarding so the bank's verification calls go to the operator.
How does it get around Android protections?
CloudSEK says the first-stage dropper asks for only three permissions, then installs the hidden payload while posing as the Play Store, so Android 13 and later treat it as a store install and skip Restricted Settings. CloudSEK links this to ThreatFabric's 2023 SecuriDropper research. It also says the dropper disables the Play Protect verifier and routes Play Store traffic into a dead local VPN tunnel.
What should I do if I installed one of these apps?
CloudSEK's advice: dial ##002# to cancel all call forwarding, block the card through the bank's official channels, uninstall the app, and report it at cybercrime.gov.in or by calling 1930. Then check your SMS for OTPs you did not request and tell your bank which card details you typed into the page.
What should banks and card issuers do?
CloudSEK recommends blocking its indicators at network, email and mobile threat-defence layers; monitoring for call-forwarding activation and new-device OTP use around card-not-present transactions; publishing an advisory that names the only official app package and warns against sideloading; and reporting hosting, Firebase and Telegram abuse quickly, because new branded APKs can be built in minutes.
Is this the same as MR ROBOT or CyberDakait?
CloudSEK does not link the Party panel to other operations, and its report names no malware family. MR ROBOT (another rent-a-trojan service aimed at Indian bank customers, described in an earlier CloudSEK report) and Group-IB's CyberDakait cluster are separate reports by other researchers. Treat them as the same pattern, not the same operator.
Practise it
- Android Security Lab: what a sideloaded banking trojan changes on a phone.
- Online Banking Security Lab: OTP theft, call forwarding and card-not-present fraud from the bank's side.
- Mobile log triage: read the device evidence.
Related coverage: AU Small Finance Bank data leak claim and bank cyber incidents in November 2026.
Sources
- CloudSEK: Inside the 'Party' panel, how fraudsters rent Android banking trojans to target Indian bank customers (20 Nov 2026)
- CloudSEK: Inside MR ROBOT, malware-as-a-service targeting Indian bank customers (separate operation)
- Group-IB: CyberDakait, seven Android trojan families targeting Indian banking apps (separate cluster)