The images in this article were generated with artificial intelligence. How we publish
A new wave of fraud is taking advantage of user confidence in bank application updates to distribute variants of Android malware known as NFCShare which is now hosted in public repositories such as GitHub and presented as legitimate "updates" of European banks. Unlike attacks that only record keys or kidnap sessions, this family has evolved to exploit the NFC hardware of the phone and read contact card data using the IsoDep interface and EMV commands, capturing not only the number and expiry date, but also the four-digit PIN that the victim introduces into a fraudulent screen.
The modus operandi combines phishing web and social engineering techniques: the victim reaches a page that imitates the bank, introduces credentials or receives instructions to "verify" your card and then is asked to download an APK from a GitHub link. In some incidents, the use of calls or SMS from actors who pose as bank employees to strengthen pressure was observed. Once installed, the application shows screens that induce the card to approach the smartphone NFC chip; the read data is sent to a control server via a WebSocket channel, facilitating its immediate use in relay or fraud schemes.

The researchers following the case, including the team that initially documented it, have observed an increase in the range of objectives: from an original attack on a single entity to campaigns that mimic multiple bank apps in Italy and Spain. In addition, recent samples incorporate deliberately malformed APK packaging to confuse automatic analysis tools, a technique that does not make manual analysis impossible but does increase friction for detectors and scanning platforms.
The implications are strong: a compromised phone can become a tool for clone or non-contact payment relay and the combination of card data with the PIN facilitates fraudulent transactions or their sale in criminal markets. Operations are not limited to a country or a single financial entity, so customers in any jurisdiction using contact cards must assume that the threat exists and take action.
In the area of user prevention, a number of basic but effective precautions should be applied: to download bank applications only from official stores, to check with the bank any urgent requests for "update" and to distrust external links offering APKs. It is also recommended disable NFC when not used, do not close contact cards to the phone unless the operation is legitimate and activate system protections like Play Protect. For technical references and official advice about NFC on Android, the developer or user can consult the Android documentation: https: / / developed, and Google Play Protect security recommendations are available at: https: / / support.google.com / googleplay / ansher / 2812853.

For security teams and banks, the campaign leaves operational lessons: security controls should include detection of abnormal downloads from public platforms, blocking and analysis of APKS with atypical packaging, and monitoring of WebSocket output patterns to non-supplier hosts. Financial institutions should intensify customer warning campaigns, provide verifiable channels for communication verification and strengthen authentication in sensitive transactions to reduce the impact of committed credentials or card data.
If you think you could download a malicious app or if you have been asked to scan your card as "verification," contact your bank immediately, register the incident and request the preventive blocking of the means of payment. Early warning and limitation of operations dramatically reduce the ability of attackers to monetize the information obtained by this type of malware.
Public analyses that have documented this behavior help to understand the evolution of the threat; for more context and a technical report on NFCShare, see the research published by the team that followed it: https: / / www.d3lab.net / nfcshare-android-trojan-nfc-card-data-theft-via-malicious-apk /. Keeping the defenses up to date, educating users and restricting the NFC exposure area are measures that will mitigate the effectiveness of these campaigns.
Related
More news on the same subject.

FBI and six countries link Integrity Technology Group to entity post theft in SE Asia
On October 8, the FBI and agencies in six countries issued a joint warning that assigns to a Chinese company, Integrity Technology Group, a sustained series of intrusions whose ...

Campaign with LLM and ARTEX attacks South Korean financial institutions and exfilters data
Security researchers have documented a campaign directed against South Korean financial institutions using language-driven attack tools to automate intrusions and data extractio...

ChainDrop campaign exposes tensorlake in npm; version 0.5.144 withdrawal
A package of npm called tensorlake, an SDK in TypeScript oriented to Tensorlake applications and services, was engaged in a supply chain campaign linked to the attack family kno...

Google reports DNS kidnapping: TLS certificates for google.com.gh, google.sl and google.as
Google reported on October 6 that attackers managed to issue unauthorized HTTPS certificates for Google and YouTube names after compromising authoritative DNS records of three t...

Cyber risk in 2026 moves to workflows and IA, according to Voice of the CISO
The data added by five editions of the Voice of the CISO study - including the most recent findings of 2026 - draw a less intense change than risk location: the threat is moving...

Phishing BitB points to advertising professionals and account managers to steal MFA
Security researchers have described a phishing campaign for advertising professionals and account managers that uses a human-operated platform to mimic ad products linked to IA ...

LibreOffice / OpenOffice Calc allows remote source execution when opening ODB / JDBC leaves
Researchers have shown that a malicious spreadsheet can force LibreOffice and Apache OpenOffice to run code controlled by an attacker at the time the file is opened, without sho...