Apalrd has done some great "popular computer science" videos on the various remote KVM devices that is well worth looking up. One of them specifically goes into the ridiculously sketchy methods that are used to fetch and execute unsigned code in random buckets to handle firmware updates.
But as for the mic? Honestly, if you open up a LOT of consumer devices you are going to find random microphones. Not because they are all secretly spying on you. But because they use "off the shelf" chips and boards that already have those embedded. Especially since microphones and speakers are kind of the same hardware in most cases and we ALL love a good beep.
I 100% agree the software stack shouldn't be on there. But, as the blog post points out, there is a LOT of developmental code and packages in that image that shouldn't be. It is likely just a case of not removing unnecessary packages from the base image.
Because... the entire point of a device like this is that you plug it in somewhere you aren't. MAYBE JetKVM corp can hear me muttering profanity or wondering where I left that USB c splitter when I am trying to assemble it the first time. The rest of the time? It is plugged into the back of a server that I am booting up so that I can install proxmox without having to drag a monitor over. And while you can potentially get some juicy info out of that? It is not at all worth the hassle to set up fake companies and market a fake (moderately high demand in the right circles) device.
