203

Malicious Plugin in Pidgin (Chat Application) (pidgin.im)

submitted 2 months ago by pnutzh4x0r@lemmy.ndlug.org to c/opensource@lemmy.ml

16 comments fedilink hide all child comments

Greetings everyone. It is with much regret that I am writing this post. A plugin, ss-otr, was added to the third party plugins list on July 6th. On August 16th we received a report from 0xFFFC0000 that the plugin contained a key logger and shared screen shots with unwanted parties.

We quietly pulled the plugin from the list immediately and started investigating. On August 22nd Johnny Xmas was able to confirm that a keylogger was present.

you are viewing a single comment's thread
view the rest of the comments

[-] Telorand@reddthat.com 89 points 2 months ago

It went unnoticed at the time that the plugin was not providing any source code and was only providing binaries for download. Going forward, we will be requiring that all plugins that we link to have an OSI Approved Open Source License and that some level of due diligence has been done to verify that the plugin is safe for users.

Unfortunate that this happened, but at least they are forcing more transparency to try to minimize the ability to hide behind opaque code.

[-] __forward__@lemm.ee 29 points 2 months ago

Without some sort of reproducible builds (which are really finnickey to actually get) this doesn't really help though. Adding some set of malicious patches before doing the binary release is trivial.

[-] wizardbeard@lemmy.dbzer0.com 16 points 2 months ago

I agree that reproducible builds would be ideal and modifying binary releases is trivial, but any step forward is better than no review process at all.

There's no such thing as a perfect system. It's all about increasing the number of hoops for an attacker to jump through. This is at least a step in the right direction.