This command works well for me
ioreg -l -w 0 | grep SecureInput | awk 'BEGIN {FS="[^a-zA-Z0-9]+"} {print $8}' | uniq | xargs -n 1 ps aux
And to kill it:
ioreg -l -w 0 | grep SecureInput | awk 'BEGIN {FS="[^a-zA-Z0-9]+"} {print $8}' | uniq | xargs -n 1 kill
Also, thanks to everyone on this thread! What an awesome community!
I also want to share that this is kind of a sad reality for me, because my company's VPN client, turns on SecureInput while it is running, even if not connected to the VPN. Also, killing it does not help for long, because some unknown process keeps it auto-starting. So many of my macros (particularly ones that provide direct keyboard input when triggered) are useless unless I: Rename the app, kill it, do my work with all my glorious macros, rename the vpn client back to its original name (which triggers the autostart).
Anyways, it would be nice to turn off the "honoring" of the SecureInput system setting in Keyboard Maestro. Or at least whitelist certain sources of it being turned on. (I notice that Keyboard Maestro is able to detect the culprit since it displays it correctly on the warning message when I open the editor. Perhaps it would not be difficult to add a whitelisting feature.)
Cheers!