Tag Archive for: wallet

Android 14 QPR1 Beta 1 seems to break Google Wallet

/in


google wallet security

Google released the first beta to Android 14 QPR1 last night for Pixel phones, but eager testers should be aware that Google Wallet isn’t currently functional.

NFC payments via Google Wallet are a useful part of almost any Android phone, and with more and more merchants accepting that as a form of payment, many have come to rely on the functionality in their day to day. However, running early or rooted software can often result in the device failing to meet security requirements, and, as such, blocking Wallet from actually working.

While Android 14’s beta program largely worked with Google Wallet, that’s not the case for the first QPR1 beta.

On my Pixel Fold, opening the Wallet app results in a pop-up saying that the “device doesn’t meet security requirements” and that “you can’t tap to pay with this device.” Attempting to add a new card results in a similar error.

Notably, Wallet didn’t purge any of the cards I already had set up for NFC payments on my Pixel Fold, nor does it seem to indicate that they won’t work. It only tells me that I can’t add a new card. That said, I’d guess that tap to pay would be blocked if I actually tried to use it.

Update: Shortly after this story went live, some readers chimed in that Google Wallet is still working, so your results may vary.

If Google Wallet payments in-store are a crucial part of your day-to-day, it’s certainly for the best that you avoid installing Android 14 QPR1, at least until this gets fixed in forthcoming updates as it usually does.

More on Android:

FTC: We use income earning auto affiliate links. More.

Source…

Atomic Wallet Hack Exposes $35 Million Crypto Asset Theft – An In-depth Look at the Aftermath and Ongoing Investigation

/in


Join Our Telegram channel to stay up to date on breaking news coverage

The Atomic Wallet hack has shaken the crypto community, causing substantial user losses and prompting an urgent investigation. Here’s a closer look at the aftermath, recovery efforts, and the wider landscape of cryptocurrency breaches, along with Atomic Wallet’s response to the incident.

Atomic Wallet Hack Reveals $35 Million in Crypto Asset Theft

An analysis conducted by on-chain investigator ZachXBT reveals that Atomic Wallet users have suffered crypto asset theft amounting to at least $35 million since June 2. Among these losses, the five largest account for $17 million.

After the attack, Atomic Wallet took to Twitter to inform users that they were actively conducting an investigation into the cause of the incident. Troubling accounts have surfaced, revealing instances of token losses, erasure of transaction histories, and even the outright theft of entire crypto portfolios.

ZachXBT, a pseudonymous Twitter user known for tracking stolen crypto funds and aiding hacked projects, independently conducted an investigation. According to ZachXBT’s findings, the largest victim lost $7.95 million in Tether (USDT). ZachXBT commented that the total amount stolen could potentially exceed $50 million as more victims continue to be discovered.

Atomic Wallet Hack Reveals $35 Million in Crypto Asset Theft

An image shared by ZachXBT on Twitter showcases his investigation into Atomic Wallet’s hack, offering further evidence of the breach.

Atomic Wallet has a user base of over 5 million individuals worldwide. In an interview, a long-time user named Emre, who happens to be a cybersecurity professional, shared his experience as a victim of a security breach.

Emre expressed deep distress after losing nearly $1 million in crypto assets obtained from bug bounty programs. The stolen tokens encompass Bitcoin (BTC), Dogecoin (DOGE), Litecoin (LTC), Ether (ETH), USDT, USD Coin (USDC), BNB, and Polygon (MATIC).

Emre highlighted the lack of concrete updates from Atomic Wallet regarding the incident. While the company claims to be investigating the matter, victims like Emre are still awaiting tangible progress. The funds stored in Atomic Wallet were intended for the establishment of…

Source…

Atomic Wallet hack losses top $35M, on-chain sleuth reports

/in


At least $35 million worth of crypto assets have been stolen from Atomic Wallet users since June 2, according to an analysis from on-chain sleuth ZachXBT. The five largest losses account for $17 million.

According to Atomic Wallet on Twitter, the cause of the attack is being investigated. Reports have surfaced of tokens being lost, transaction histories being erased, and even entire crypto portfolios being stolen.

An independent investigation carried out by pseudonymous Twitter ZachXBT, known for tracing crypto stolen funds and assisting hacked projects, has found the largest victim lost $7.95 million in Tether (USDT). “Think it could surpass $50m. Keep finding more and more victims, sadly,” commented ZachXBT.

Screenshot: ZachXBT’s investigation into Atomic Wallet’s hack. Source: ZachXBT on Twitter.

Atomic Wallet claims to have over 5 million users around the world. Cointelegraph spoke with a long-time Atomic’s client who is now a victim of the security breach. “I felt terrible because I am a cybersecurity expert by profession,” said Emre, a Turkish resident who lost nearly $1 million in crypto assets received from bug bounty programs. His stolen tokens include Bitcoin (BTC), Dogecoin (DOGE), Litecoin (LTC), Ethereum (ETH), USDT, USD Coin (USDC), Binance Coin (BNB), and Polygon (MATIC).

“They say they’re looking into it, but they don’t have anything concrete yet,” Emre continued. The funds held at Atomic Wallet were destined for the establishment of a cybersecurity firm in Turkey.

Atomic is a noncustodial-decentralized wallet, meaning users are responsible for assets stored in the application. As usual, its Terms of Service do not accept any liability for on-chain damages suffered by users. “Under no circumstances will Atomic Wallet be liable to you for damages arising out of the services exceeding $50,” says one excerpt.

There has been little…

Source…

TSA Now Accepts Mobile IDs in Google Wallet on Android Mobile Devices, Starting with Maryland

/in


In collaboration with the State of Maryland and Google, the Transportation Security Administration (TSA) now accepts Maryland-issued mobile driver’s licenses and ID cards in Google Wallet on Android mobile phones at select TSA airport security checkpoints.

TSA PreCheck® passengers will be able to use this new feature at checkpoints for identity verification at 25 participating airports.

“TSA’s partnership with Google and Maryland spotlights our commitment to implementing new technologies and expanding use of mobile driver’s licenses,” said TSA Administrator David Pekoske. “This launch represents the first mobile driver’s license in Google Wallet. We continue to work closely with other states on deploying this capability across the country. TSA is committed to collaborating on international, open standards that provide enhanced security, privacy protections and offers airline passengers a more efficient and convenient travel experience.”

To present their ID in Google Wallet at select TSA checkpoints, passengers will approach the podium at the first station in the screening process. The passenger may consent to provide their mobile identification from Google Wallet by simply turning on Bluetooth and holding their Android smart phone or watch on the second-generation Credential Authentication Technology (CAT-2) reader device.  The digital identity information from the mobile driver’s license is encrypted and transmitted digitally to CAT-2, where the passenger’s real-time camera photograph will be compared against the encrypted mobile identity information from Google Wallet and their reservation data that would have been on the passenger’s boarding pass.  Once the CAT-2 confirms the identity match, a TSA officer will verify the match and the passenger will proceed to security screening – without ever exchanging a boarding pass.  TSA officers may perform additional passenger verification if needed. The real-time live camera photograph and the mobile identification information is not kept, transmitted or used for any purpose other than for the immediate identity verification by a TSA officer. Passengers who do not wish to participate in facial…

Source…