I think you've maybe misunderstood this aspect of the problem. Curiosity aside (wild guess: some form of RTOS, or possibly Linux/BSD, running on an ARM architecture), OP was talking about part of the DJI Assistant software installed locally on their PC, not a firmware blob that would be downloaded to the drone.
There are numerous instances of various executables and DLLs in the DJI Assistant installation triggering FPs in AV software, BitDefender being particularly common, although not the only one. That can be quite scary for a layperson (OP did at least realise it was probably an FP and was looking to confirm), so an high-level explaination of what's going on to calm nerves and verify whether there's actually a problem or not seems like a good idea to me.
Really, DJI needs to be a bit more proactive in fixing this. They're not a small company, it's a mostly solved problem, and their own forums contain multiple instances of people with the problem so they can hardly be unaware of the issue. I can understand the occassional unsigned executable slipping through to release, or an FP here and there, but this is a frequent enough occurance it's now just making DJI look sloppy.