ABSOLUTE LOJACK BLOCK HOW TO
ABSOLUTE LOJACK BLOCK UPDATE

I haven't confirmed whether the same is true for the complaints on the HP Drive Encryption software and the unknown installer (which I believe is related to the HP software), but I would believe so. With PUA detection disabled, no complaints are given on the UEFI. It's probably worth noting that ESET didn't detect the Computrace variants as malware, but as a PUA (Potentially Unsafe Application). I've double checked the product specifications, and the laptop ships with Intel AT turned off by default, so I think that may solve the question of how Computrace got there (there by default)

ABSOLUTE LOJACK BLOCK UPDATE

My computer is an HP ProBook 4540s, where the last shipped BIOS update was on ~July 2017, so I think that rules out a recent update introducing the issue. They haven't reported any issues in the past. The System Startup File Checks are still enabled, and report their last run time as of earlier today. The latest scan was run with detection engine 18058

ABSOLUTE LOJACK BLOCK HOW TO

The log records the detection engine as 17982, but I'm not sure how to translate that into a version number. I do not know what the retail version of ESET was for the 9/1 scan. To answer your questions in the order posed: So you want to first check if this is the case. If Computrace does indeed exist, there is also the possibility that it arrived on your device via a recent manufacturer BIOS/UEFI firmware update. It is definitely not something you want on your PC if this is indeed the case. Here's is a Blackhat conference presentation on Computrace: . Unless you disabled this scheduled scan, I find it odd that Smart scanning did not detect your UEFI malware but your full system scan did. This scan runs each time you boot your PC. It could also mean that UEFI/BIOS detection has improved in 11.2.63.įinally, Eset's default Smart scanning does scan the OS installation drive BIOS/UEFI by default.

When you did the full scan on 9/1, were you on version 11.2.49 assuming you're running a retail version of Eset? Was the UEFI malware detection made on version 11.2.63? This could be a false positive issue with 11.2.63. Some motherboards have dual UEFI/BIOS setups which allow you to restore from the backup UEFI/BIOS. Eset's recommended mitigation for UEFI malware is to update your motherboard firmware.

Absolute lojack block