Hello everybody. I'm in a trial period for Bitdefender Total Security. After checking Virustotal gave the following return of the executables below. Is something wrong? Thanks.
"C:\Program Files\Bitdefender\Bitdefender Security\hntwhlpr.exe"
Crowdsourced YARA rules
-Matches rule INDICATOR_SUSPICIOUS_VM_Evasion_MACAddrComb by ditekSHen from ruleset indicator_suspicious at https://github.com/ditekshen/detection Detects executables referencing virtualization MAC addresses
"C:\Program Files\Bitdefender\Bitdefender Security\obkch.exe"
Crowdsourced YARA rules
-Matches rule Adobe_XMP_Identifier by InQuest Labs from ruleset Adobe_XMP_Identifier at https://github.com/InQuest/yara-rules-vt This signature identifies Adobe Extensible Metadata Platform (XMP) identifiers embedded within files. Defined as a standard for mapping graphical asset relationships, XMP allows for tracking of both parent-child relationships and individual revisions. There are three categories of identifiers: original document, document, and instance. Generally, XMP data is stored in XML format, updated on save/copy, and embedded within the graphical asset. These identifiers can be used to track both malicious and benign graphics within common Microsoft and Adobe document lures.
"C:\Program Files\Bitdefender\Bitdefender Security\wsccommunicator.exe"
Crowdsourced Sigma Rules
-Matches rule File deletion via CMD (via cmdline) by Ariel Millahuel at SOC Prime Threat Detection Marketplace Detects "cmd" utilization to self-delete files in some critical Windows destinations.
-Matches rule Failed Code Integrity Checks by Thomas Patzke at Sigma Integrated Rule Set (GitHub) Code integrity failures may indicate tampered executables
"C:\Program Files\Bitdefender\Bitdefender Security\wsccommunicator_ls.exe"
Crowdsourced Sigma Rules
-Matches rule Failed Code Integrity Checks by Thomas Patzke at Sigma Integrated Rule Set (GitHub) Code integrity failures may indicate tampered executables.
