Traces left behind by ksu module after install/uninstall

[NeverSm1le]

May I ask what ksu do when install/uninstall modules, because my banking app somehow pick up this "trace".
It works with ksu no module, but when you install any mudule it will detect root and refused to run. Uninstall modules and it still refuse to run, even with clear data/reinstall. YASNAC still show passing basic intergrity so I guess it must pick up something.
Magisk get detected immediately, even with hide.
The app in question: link, support English and Vietnamese. Just put in any random 10-number phone number start with 0 (0xxxxxxxxx), if it can detect the slightest trace it will tell you the device is invalid.

[Bot-wxt1221]

It is possibly caused by /system mount point.

What's your kernel version?

If it is under 4.19 .Try this #955 (comment)

Bug3:UMOUNT for Kernel under 4.4

[NeverSm1le]

Gave root access to momo then turn it off made it work, here's the screenshot

Sadly still know nothing

[Bot-wxt1221]

Do the same work as Momo to that app

[NeverSm1le]

Too bad it still doesn't work, guess I have to get used to no module life..

[Bot-wxt1221]

Could you give the output of

cat /proc/self/mounts
cat /proc/self/mountinfo
cat /proc/self/mountstat

In termux, do not give root pemission to termux.

[hereblur]

I found this issue too with zygisknext.
Root Not detect before install.
After disabled or uninstall it’s still detected.
Luckily Shamika hide it for me.