An open source project used by people capable of analyzing the network and disk I/O of binaries they run doesn't sound like a good target -- if something was found it would have massive consequences.

Backdoors from TLAs don't look like backdoors.

People who use Ghidra know that backdoors from TLAs don't look like backdoors.

I wouldn't say this is true at all, there are lots of kids out there who will cut their teeth with this seeing as it is entirely free.

Also, it is as if people forget the launch of Ghidra; https://github.com/NationalSecurityAgency/ghidra/issues/6

Hiding a backdoor requires hiding it from every user who might publicize it, not some users.

Your issue (which is barely a vulnerability at all, in my personal opinion) demonstrates a failure to hide a vulnerability, if you think it was intentionally-placed (which I don't), in that you quickly learned about it.

I can't imaging a project aimed at reverse engineers would be the best place to try to hide that sort of thing. Ghidra is open source, you are free to audit and build it yourself if you are concerned.

Not to take away from your point, but a lot of "career" reverse-engineers are no more knowledgeable about the details of their tools or the low-level than developers.

> Ghidra is open source, you are free to audit and build it yourself if you are concerned.

^ the manyeyeballs fallacy

I don’t think the many eyes fallacy states that code audits are impossible or useless.

but it states that nobody (as in nearly not enough people) does it

There was one possible backdoor in the past :

https://latesthackingnews.com/2019/03/24/critical-vulnerabil...