205
Motorola phones are hijacking your Amazon app [Video]
(9to5google.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 26 May 2026
205 points (96.0% liked)
Technology
85016 readers
3017 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 3 years ago
MODERATORS
Yeah, I didn't understand. Sorry about that.
I could potentially see this happing if it's an app that this app talks to that's compromised or perhaps if they have a second app installed that this app interfaces to/that is talking to this app to prompt this behavior.
It wasn't clear to me if they attempted to duplicate this on the same hardware by wiping the device and then side loading the app/installing it from a different app store.
But I think that's because this app is a stock app that can't generally be deleted (only rolled back to a previous version) from my understanding. But I may be wrong about that. This definitely makes it sound like it was the most recent update that caused this behavior.
Yeah, it's a bit confusingly worded. A couple paragraphs down it starts to show how the behavior isn't consistent
Just the fact that the same version installed other ways didn't have the same behavior makes an app compromise conclusion hard to support. But you're entirely right that this could be secondary app caused, potentially the update mechanism on the phone was compromised, which might explain why side loading didn't have the same behavior.