Sadly those tools would have been inadequate as this was a truly zero-day file and had a legitimate certificate as well (the latter is what could really cause detection issues for some).
This particular attack is troubling as it mimics in many ways how Nation State malicious attacks are created. Those responsible had to code the malware, acquire a certificate, code the popper, setup a Server, and somehow gain Admin control of the website to insert the popper. These things are not done either cheaply or without great organization.
Any person (or cat) can code a stealer, but not many can do this.
Hey CS! VS should have absolutely no problem blocking this file, whether it is ON or OFF (like in Smart Mode). I could not find the sample or the signer in the database, so it looks like it has not been tested against VS. If you get a chance, please test the file with VS. VS will block the file, although I would be curious what the WhitelistCloud and VoodooAi results are (just out of pure curiosity... it is still going to be blocked). Please remember, VS does not auto allow on signature alone, whether it is verified or not. If VS does not block this file for some odd reason, please let me know because that would mean there is a bug I need to fix. Thank you!
Edit: I forgot the mention, the VS prompt will be very similar to the CF, in that it will say "There is an issue with the digital signature that is signed by Sichuan Niurui Science and Technology Co., Ltd. The digital signature cannot be verified by CyberLock."
BTW, when VS is ON, it is going to block this file either way.
When VS is OFF, it is a little different story, but VS should block this file as well.
The only way this file is going to be auto allowed when VS is OFF is if...
1) The digital signature is verified
2) The digital signature is verified by VoodooShield
3) The file has a Safe WhitelistCloud verdict
4) The file has a Safe VoodooAi verdict
5) I think there are a couple of other checks, I can look them up if interested.