textslashplain.com/2024/11/15/b...
textslashplain.com/2024/11/15/b...
Tip: one shouldn’t add to your MSI that the CABs are signed. This slows down install a lot and doesn’t serve any good purpose.
Tip: one shouldn’t add to your MSI that the CABs are signed. This slows down install a lot and doesn’t serve any good purpose.
www.elastic.co ->
Original->
www.elastic.co ->
Original->
The issue? A false positive marker collision broke validation.
💡 Lesson: Always validate signatures in CI/CD and know that legacy detection logic can still trip you up.
The issue? A false positive marker collision broke validation.
💡 Lesson: Always validate signatures in CI/CD and know that legacy detection logic can still trip you up.
Windows can incorrectly flag signed binaries as malformed due to a decade-old heuristic that scans for hardcoded 'invalid markers' within the signature block.
-
IOCs: (None identified)
-
#Authenticode #ThreatIntel #Windows
Windows can incorrectly flag signed binaries as malformed due to a decade-old heuristic that scans for hardcoded 'invalid markers' within the signature block.
-
IOCs: (None identified)
-
#Authenticode #ThreatIntel #Windows
Or: How threat actors impersonate companies to obtain authenticode certificates for signing their malware.
And why revokation is important.
squiblydoo.blog/2024/05/13/i...
Or: How threat actors impersonate companies to obtain authenticode certificates for signing their malware.
And why revokation is important.
squiblydoo.blog/2024/05/13/i...
The Baseline Requirements define revocation conditions based on use in the wild, not the developer’s intent.
Ship signed code? Design it to resist abuse — attackers can weaponize your trust, and your cert can be pulled.
The Baseline Requirements define revocation conditions based on use in the wild, not the developer’s intent.
Ship signed code? Design it to resist abuse — attackers can weaponize your trust, and your cert can be pulled.
learn.microsoft.com/en-us/window...
learn.microsoft.com/en-us/window...
the bad thing about them is that this is somehow the second time the uefi firmware updater has a valid authenticode signature and all but not matching the listed hashes?
the bad thing about them is that this is somehow the second time the uefi firmware updater has a valid authenticode signature and all but not matching the listed hashes?
"Hackers turn ScreenConnect into malware using Authenticode stuffing" #bolhasec
"Hackers turn ScreenConnect into malware using Authenticode stuffing" #bolhasec