this post was submitted on 01 Dec 2025
49 points (100.0% liked)

Technology

5334 readers
51 users here now

Which posts fit here?

Anything that is at least tangentially connected to the technology, social media platforms, informational technologies and tech policy.


Post guidelines

[Opinion] prefixOpinion (op-ed) articles must use [Opinion] prefix before the title.


Rules

1. English onlyTitle and associated content has to be in English.
2. Use original linkPost URL should be the original link to the article (even if paywalled) and archived copies left in the body. It allows avoiding duplicate posts when cross-posting.
3. Respectful communicationAll communication has to be respectful of differing opinions, viewpoints, and experiences.
4. InclusivityEveryone is welcome here regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.
5. Ad hominem attacksAny kind of personal attacks are expressly forbidden. If you can't argue your position without attacking a person's character, you already lost the argument.
6. Off-topic tangentsStay on topic. Keep it relevant.
7. Instance rules may applyIf something is not covered by community rules, but are against lemmy.zip instance rules, they will be enforced.


Companion communities

!globalnews@lemmy.zip
!interestingshare@lemmy.zip


Icon attribution | Banner attribution


If someone is interested in moderating this community, message @brikox@lemmy.zip.

founded 2 years ago
MODERATORS
top 9 comments
sorted by: hot top controversial new old
[–] apotheotic@beehaw.org 8 points 1 month ago (1 children)

I'm having a moment - do users need to manually install the app again to receive the new version with the new digital signature associated?

[–] King@blackneon.net 6 points 1 month ago (1 children)

Yes, exactly.

You need to manually install the new version with the new signature.

[–] apotheotic@beehaw.org 2 points 1 month ago
[–] BrikoX@lemmy.zip 5 points 1 month ago (2 children)

The title doesn't match the facts in the announcement.

Only signature of the developer was leaked which could have lead to unsafe releases, but the point is moot as the developer is changing the signature key moving forward.

[–] breakingcups@lemmy.world 7 points 1 month ago (1 children)

There's a lot unclear, but it seems that an actual compromised update was released on official infrastructure (and subsequently removed from some devices by Play Protect). A transparency statement from the developer is still forthcoming. I'm not risking anything, not even updating to the new app, until all the dust has settled.

[–] BrikoX@lemmy.zip 1 points 1 month ago* (last edited 1 month ago) (1 children)

The app id is being changed, so there is no way to push new updates with that signature anymore. Hence the need to re-install the app.

Also it looks like the developer is adding VirusTotal scan workflow for all new releases moving forward.

That said, I'm not familiar with the developer or the situation enough to comfortably say it's safe.

[–] AmbiguousProps@lemmy.today 2 points 1 month ago* (last edited 1 month ago)

I'm not concerned about the app id changing after a signature leak, in fact, it's what I'd expect. I am concerned about if the new signature is from the actual dev or not, and the dev hasn't really said much other than they'll release a disclosure once their new build is pushed to fdroid. It's been pushed as far as I can tell, and it's still been silence from them. I'd recommend not installing either app until this gets sorted out, and revoking the app's access to your account.

[–] King@blackneon.net 1 points 1 month ago

I edited the title to be more specific.

[–] AmbiguousProps@lemmy.today 1 points 1 month ago* (last edited 1 month ago)

Slightly more detail in this GitHub issue, however much is still unknown, even after three or so days. The dev hasn't revealed any further details. Some articles on this incident:

Note that the articles provide little detail on what's happened, mostly just detail that a malicious library was found and Play Protect started removing the app if affected. It's unclear which versions are specifically affected, how the dev got breached, and what the malware actually does. According to a user (who may or may not be using some sort of LLM, their comment sounds like one at least) in a separate, related issue, the malware may collect device info and send to a command & control server. It could (in theory) receive new instructions at any point if it's a C2 server. Again, it does appear that they had an LLM of some sort generate their comment, so take it with a grain of salt.

I'm going to uninstall the app and revoke access on my Google account page. I see little reason to need to reset my password as of right now, since the app uses an API key and not my actual password. In my opinion, it's possibly related to YT viewbotting and commenting, or to add your device to a botnet. It's unclear to me how this botnet would work in practice, since even Android TV sandboxes apps (for the most part)