So, the “last update” was built from ac41318, since then there were exactly 2 commits:
Both do not immediately look malicious. So, either the release is poisoned (in which case you can build it from source and see if still detected), or the repo was poisoned before, and the payload didn’t activate until those changes, or AVs decided to crackdown on random shit running their code in other law-abiding processes’ address space 🤣
=> More informations about this toot | View the thread | More toots from fl42v@lemmy.ml
=> View DoctorButts@kbin.melroy.org profile
text/gemini
This content has been proxied by September (3851b).