[GH-ISSUE #53] Anti-Virus Flagging pgAdmin3 #46

New issue

Open

opened 2026-05-05 03:33:03 -06:00 by gitea-mirror · 2 comments

gitea-mirror commented

2026-05-05 03:33:03 -06:00

Owner

Originally created by @winmedatgmaildotcom on GitHub (Oct 7, 2025).
Original GitHub issue: https://github.com/levinsv/pgadmin3/issues/53

Carbon Black Defense (the anti-virus component) is flagging pgadmin3-master\x64\release\pgadmin3.exe for accessing the WinAPI function SetWindowsHookEx. It states adversaries may use this API to perform keylogging.
Can you please elaborate on why pgAdmin3.exe is calling that API (SetWindowsHookEx), and can it be resolved?
Thanks.

Originally created by @winmedatgmaildotcom on GitHub (Oct 7, 2025). Original GitHub issue: https://github.com/levinsv/pgadmin3/issues/53 Carbon Black Defense (the anti-virus component) is flagging pgadmin3-master\x64\release\pgadmin3.exe for accessing the WinAPI function SetWindowsHookEx. It states adversaries may use this API to perform keylogging. Can you please elaborate on why pgAdmin3.exe is calling that API (SetWindowsHookEx), and can it be resolved? Thanks.

gitea-mirror added the

question

label 2026-05-05 03:33:03 -06:00

gitea-mirror commented

2026-05-05 03:33:09 -06:00

Author

Owner

@levinsv commented on GitHub (Oct 8, 2025):

The pgadmin3 source code does not contain SetWindowsHookEx calls.
But they are in the shared wxWidgets library (wxmsw32u_core_vc14x_x64.dll ).
I think that the anti-virus will react this way to any application using this library.
If you have questions about code security, you can always look for unsafe calls in the source codes.

@levinsv commented on GitHub (Oct 8, 2025): The pgadmin3 source code does not contain SetWindowsHookEx calls. But they are in the shared wxWidgets library (wxmsw32u_core_vc14x_x64.dll ). I think that the anti-virus will react this way to any application using this library. If you have questions about code security, you can always look for unsafe calls in the source codes.

gitea-mirror commented

2026-05-05 03:33:12 -06:00

Author

Owner

@winmedatgmaildotcom commented on GitHub (Oct 8, 2025):

Thank you for getting back to me. Much appreciated!

I was also reading this somewhere. "Use static linking: If you are a developer compiling your own wxWidgets application, configure your project to use static linking. This embeds the required wxWidgets code directly into your executable, eliminating the need for the wxmsw32u_core_vc14x_x64.dll file at runtime. "

Thank you again for your excellent work and for keeping and maintaining this tool current and up-to-date.

@winmedatgmaildotcom commented on GitHub (Oct 8, 2025): Thank you for getting back to me. Much appreciated! I was also reading this somewhere. "Use static linking: If you are a developer compiling your own wxWidgets application, configure your project to use static linking. This embeds the required wxWidgets code directly into your executable, eliminating the need for the wxmsw32u_core_vc14x_x64.dll file at runtime. " Thank you again for your excellent work and for keeping and maintaining this tool current and up-to-date.