11–20 of 24 posts
IMHO Pretty great of dbrand to step in and sponsor a topically sensitive video on short notice as well as provide a pretty big carrot to bring in a flood of traffic. Just ordered a matte black skin for my MBP 14". I have no relation to dbrand other than being an occasional customer.
IMHO Pretty great of dbrand to step in and sponsor a topically sensitive video on short notice as well as provide a pretty big carrot to bring in a flood of traffic. Just ordered a matte black skin for my MBP 14". I have no relation to dbrand other than being an occasional customer.
[flagged]
[flagged]
Earlier quoted context omitted.
How is this possible? Can someone point me in the direction of what mechanism is used here. If I open a pdf in chrome for example am I opening myself up to this kind of attack?
I would say first thing is to disable Windows Explorer from hiding the extension of files. From what I understand, it was an executable inside a zip attachment to an email disguising itself as a partnership proposal from a reputable source. The file inside the zip probably had a .pdf.exe extension. By default, Windows Explorer would show it as a .pdf, making it easy to run by mistake.
Is there some kind of a sandboxed pdf viewer, that could prevent infected pdf access to the rest of the computer?
From what he describes, the file disguised itself a PDF but may have been an executable instead, so the PDF viewer was probably never launched. I blame Windows hiding the extension of known files by default. `anything.pdf.exe` would show as `anything.pdf` Can't blame people from thinking it's a PDF. Otherwise, I use SumatraPDF as a viewer. Small, no frills, probably less of a vulnerability target than Adobe Acrobat.
Thanks, bitcoin.
Is there a link to the sample on VirusTotal?
Why didn't their email-service's anti-virus pick up on virus?
In the case that it was in a zip, why didn't said anti-virus extract the zip & scan?
In the case of a password-protected zip, why didn't the computer scan the file upon extraction?
In the case of a scan upon extraction, why was it missed? Outdated definitions or zero day?
We do enable Impossible Travel in Okta by default for our clients.