this post was submitted on 26 May 2026
192 points (95.3% liked)

Technology

84961 readers
3652 users here now

This is a most excellent place for technology news and articles.

Our Rules

  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. 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.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots

founded 3 years ago
MODERATORS
L3s@lemmy.world
enu@lemmy.world
technopagan@lemmy.world
L4s@lemmy.world
L3s@hackingne.ws
192
Motorola phones are hijacking your Amazon app [Video] (9to5google.com)
submitted 2 days ago by mettwurstkaninchen@feddit.org to c/technology@lemmy.world
61 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] Passerby6497@lemmy.world 2 points 15 hours ago* (last edited 15 hours ago)

Yeah, it's a bit confusingly worded. A couple paragraphs down it starts to show how the behavior isn't consistent

We verified on a Razr (2026) running an older Smart Feed v2.03.0056 that this does not happen. Our Razr Fold, with app version 2.03.0070, has started showing this behavior, so it’s the latest update that’s to blame for hijacking the user’s intent. We couldn’t replicate this on a Moto G Stylus (2026) running the same app version, though. Sideloading the app, for reasons unclear, doesn’t seem to trigger this behavior, as manually installing the updated version on the aforementioned Razr (2026) didn’t show the same behavior.

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.