Anything to worry about?
Welcome to our Community page. Thank you for your post.
I am sorry for late reply.
Could you provide us more details on aesbx. dylib? Perhaps a screenshot or a submission for F-Secure lab to analyze of the detection.
Looking forward for your reply.
Thank you and stay safe.
I get a similar experience on my MacBook seems like its a core file from f-secure's capricorn signature engine.
You can find it using:
sudo find / -name aesbx.dylib 2>&1 | grep -v "Operation not permitted"
---- results on my machine
However there seems to be a bug as the FileVault never manages to complete verification of the file
@Firmy can you confirm that this file should not be harmful?
We have checked with our team. From a quick look, the file is part of the Engine Module and it should be clean.
On the other hand, in regards to your question that there seems to be a bug, we would recommend you submit a part of aesbx.dylib to our lab for investigation. Our team will look more into this matter.
The sample submission is analyzed by our analysts and the databases will be updated if necessary.
We have an ongoing investigation in regards to this issue.
We really appreciate if you could provide us the FSDIAG for this investigation.
I will send you a private message. You may attach and send the FSDIAG to me.
Follow the steps below to generate a FSDIAG report.
If the built-in fsdiag fails kindly try the stand alone Support Tool (FSDIAG) for Mac .
Thanks for reaching out @Firmy I have send you the file now ☺️
Thank you for your cooperation.
We will look into the FSDIAG and keep you updated.