It could have been some fuzzy hash.
Yeah, possible. This is the first time I have seen BD's cloud-based detection didn't have any impact on changing hash, so this was new for me.
"Gen:Suspicious.Cloud.2.in0@auezHOh" for the main file.
"Gen:Suspicious.Cloud.4.in1@auezHOh" for the hash-changed file.
Edit: Just now checked again slightly differently with another new hash.
This time I activated BD's real-time protection when the malware was already running. Detection name via the scanner was the second name I wrote in this comment while detection name for the running malware by the real-time protection was, "Gen:Heur.Zatk.in1@buezHOh"