Malware using shared library evasion - could it affect Yara itself?

[mhuth]

There's been some cases recently of Linux malware which attempt to avoid detection via shared library evasion techniques. For example:
https://www.intezer.com/blog/research/new-linux-threat-symbiote/
https://www.intezer.com/blog/incident-response/orbit-new-undetected-linux-threat/

Could these potentially target yara itself? If so, is it recommended to statically link yara to avoid these attacks?
And is it possible to statically compile / link yara?

[mhuth]

Actually I did have a go at creating a static yara but didn't seem to have any luck.

$ export LDFLAGS="-static-libgcc -static-libstdc++"
$ export CFLAGS="-static-libgcc -static-libstdc++"
$ export CPPFLAGS="-static-libgcc -static-libstdc++"

Then configure, make, make install as usual, but its still dynamically linked.

$ file /usr/local/bin/yara
/usr/local/bin/yara: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=b1cf5d930f5a5b4fbf87b9addb68551dc2c091a2, for GNU/Linux 3.2.0, not stripped

$ ldd /usr/local/bin/yara
linux-vdso.so.1 (0x00007fff1eced000)
libyara.so.9 => /usr/local/lib/libyara.so.9 (0x00007f29dfad0000)
libcrypto.so.3 => /lib64/libcrypto.so.3 (0x00007f29df696000)
libm.so.6 => /lib64/libm.so.6 (0x00007f29df5bb000)
libc.so.6 => /lib64/libc.so.6 (0x00007f29df3b1000)
libz.so.1 => /lib64/libz.so.1 (0x00007f29df397000)
/lib64/ld-linux-x86-64.so.2 (0x00007f29dfb35000)

Are there any specific compiler / linker flags to use?