Is _Raindrop Roofing NW-protected.pdf safe?
No antivirus engine detected the encrypted PDF, but one sandbox recorded LSASS-related and process-injection telemetry that cannot be confidently attributed to the document.
All 75 antivirus engines returned no detection, including 17 tier-1 engines, and the completed sandbox assigned a clean disposition. However, saved runtime telemetry mapped activity to credential access and process injection, while the encrypted PDF is newly observed, creating an unresolved conflict that merits caution.
249e65c74e5be40302…e54ffa0b9bfac3Recommended next actions
Before opening
Do not open it until the source can be verified independently.
If you already opened it
Stop using it, scan the device, and watch for unexpected behavior or security alerts. Get a fresh copy from the original trusted source and verify its exact hash when possible.
Intelligence
The saved assessment, checked against the scan evidence and recorded coverage.
The reasoning behind this verdict
This section explains the evidence supporting the verdict and keeps conflicting or missing signals visible.
All 75 antivirus engines returned no detection, including 17 tier-1 engines, and the completed sandbox assigned a clean disposition. However, saved runtime telemetry mapped activity to credential access and process injection, while the encrypted PDF is newly observed, creating an unresolved conflict that merits caution.
Static scanning found no detection among 75 engines, including 17 tier-1 products. One completed sandbox did not issue a malicious disposition, and no inspected child was identified as malicious. Nevertheless, its telemetry includes T1003 credential access and T1055 process injection, with a heuristic specifically recording LSASS-related activity. The process list is dominated by Adobe Acrobat and Windows components, so the evidence does not establish that the PDF itself initiated those actions. Because the document is encrypted, newly observed, and has no established reputation, the behavioral conflict cannot be dismissed or confirmed from the available evidence. No complete contacted-host reputation result is available, although the runtime record contains no network contacts.
What We Detected
The PDF received 0 detections from 75 antivirus engines, including 17 tier-1 engines. It is encrypted and has only one recorded submission, so its reputation and inspectable static content are limited.
Threat Behavior
One completed sandbox assigned a clean disposition, but the saved telemetry mapped activity to T1003 credential access and T1055 process injection. A heuristic also recorded activity involving LSASS. The visible processes are primarily Adobe Acrobat and standard Windows components, making attribution uncertain; none of the three inspected child files was identified as malicious, but all three remain unclassified. No complete host-reputation cross-check is available.
What To Do Now
Do not open the document on a sensitive or production system unless its sender and business purpose can be independently verified. Keep endpoint protection enabled, update the PDF reader, and obtain a fresh copy through a trusted channel if the document was unexpected.
Where this verdict could be wrong4 caveats
- The absence of detections across 75 engines, including Microsoft, Kaspersky, ESET-NOD32, and BitDefender, weighs strongly against the concerning behavioral mappings.
- The sandbox assigned a clean disposition, and the visible process activity is dominated by Adobe Acrobat and standard Windows components.
- T1003 and T1055 may reflect activity by the document viewer or sandbox environment rather than code originating from the PDF; the supplied telemetry does not establish attribution.
- The encrypted document is newly observed, limiting both static inspection and reputation-based assurance.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- 0/75 antivirus detections
- 17 tier-1 engines reported no detection
- behaviour.hasMaliciousSandboxVerdict=false
- droppedChildren.hasMaliciousChild=false
- No runtime network contacts were recorded
- Encrypted PDF limits static-content inspection
- MITRE T1003 credential-access telemetry
- MITRE T1055 process-injection telemetry
- LSASS-related activity recorded by a behavioral heuristic
- Only one source and one submission
- Three dropped children remain unclassified
Verify the sender and expected document context before opening it, preferably using an isolated environment. Keep endpoint protection enabled and use a fully updated PDF reader.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Not runNo contacted-host reputation check is recorded.
No timestamp recordedYARA
Complete2 signature or behavior rules matched.
External intel
PartialIndependent reference checks were attempted but are incomplete.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime flight recorder
Capture complete- 1isolated sandbox run
- 14MITRE ATT&CK techniques
- 13spawned processes
- 0network contacts
- 24filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Accessed operating-system credential data, which can expose saved passwords.
High concern: Injected code into another process, a technique that can conceal execution.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Moderate concern: Communicated over a common application protocol; malware can use this for command-and-control.
Moderate concern: Checked the environment for virtualisation or analysis tools.
Note: Reads your Windows user-account details.
Note: Collects details about your system.
These are observed capabilities from an isolated analysis. A technique does not prove malicious intent on its own, and the file never ran on your device.
Attack story
Runtime observations grouped by analysis stage. Arrows organize the stages; they do not claim chronology or causality.
Input file
The submitted object
- FileObserved
_Raindrop Roofing NW-protected.pdf
249e65c74e5be40302062f484e500abd7b823fdd93dc8b0070e54ffa0b9bfac3
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Program Files\Adobe\Acrobat DC\Acrobat\Acrobat.exe" "C:\Users\<USER>\Desktop\_Raindrop Roofing NW-protected.pdf"
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Program Files\Adobe\Acrobat DC\Acrobat\Adobe Crash Processor.exe"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
acroNGLLog.txt
C:\Users\<USER>\AppData\Local\Temp\acroNGLLog.txt
04Isolated runtime analysis - Written fileObserved
NGL
C:\Users\<USER>\AppData\Local\Temp\NGL\
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
5 recorded facts from one runtime window. Every fact remains independently traceable in Analyst mode.
What this file did when executed
This file was detonated in 1 sandbox and its runtime behaviour was observed.
Adversary techniques mapped to the MITRE ATT&CK framework.
- HKEY_CURRENT_USER\Software\Classes\Local Settings\MuiCache\7b\52C64B7E\@%systemroot%\system32\wsdapi.dll,-200
- HKEY_CURRENT_USER\Software\Classes\Local Settings\MuiCache\7b\52C64B7E\@C:\Windows\System32\AppxPackaging.dll,-1001
- HKEY_CURRENT_USER\Software\Classes\Local Settings\MuiCache\7b\52C64B7E\@%SystemRoot%\System32\SessEnv.dll,-101
- HKEY_CURRENT_USER\Software\Classes\Local Settings\MuiCache\7b\52C64B7E\@%SystemRoot%\System32\CertCA.dll,-304
- HKEY_CURRENT_USER\Software\Classes\Local Settings\MuiCache\7b\52C64B7E\@%SystemRoot%\System32\CertCA.dll,-305
- C:\Users\<USER>\AppData\Local\Temp\acroNGLLog.txt
- C:\Users\<USER>\AppData\Local\Temp\NGL\
- C:\Users\<USER>\AppData\Local\Temp\Tmp8E4.tmp
- C:\Users\<USER>\AppData\Local\Temp\TmpA8B.tmp
- C:\Windows\ServiceProfiles\LocalService\AppData\Local\FontCache\Fonts\Download-1.tmp
- C:\Users\<USER>\AppData\Roaming\Adobe\Acrobat\DC\JSCache\GlobSettings
- C:\Users\<USER>\AppData\Local\Packages\Microsoft.XboxGamingOverlay_8wekyb3d8bbwe\LocalCache\KnownGameList.bin
- C:\Users\<USER>\AppData\Local\Microsoft\GameDVR\KnownGameList.update
- Global\_MSIExecute
- Global\MSILOG_8c1ce6ec1dd565aGOL.e0c11ISM_pmeT_lacoL_ataDppA_onurB_sresU_:C
- Global\AdobeCrashProcessorLocalLowLock
- \Sessions\1\BaseNamedObjects\{100184D2-BDC3-477a-B8D3-65548B67914C}_6356
- \Sessions\1\BaseNamedObjects\Local\{100184D2-BDC3-477a-B8D3-65548B67914C}_900
Files this sample writes at runtime
This file drops 3 children at runtime. None are currently flagged malicious in our cache.
- eacad3e01b8b0a44ac03…df796dNever scannednever seen before
- 513fb5d3b4195ab59af2…64de2eNever scannednever seen before
- a779a261df447a4c298c…b1b86dNever scannednever seen before
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 2rule hits recorded
- 0 / 75engines flagged
- 1sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 02
0 of 75 antivirus engines flagged the file.
ProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 1 time from 1 source.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: _Raindrop Roofing NW-protected.pdf — 249e65c74e5be40302062f484e500abd7b823fdd93dc8b0070e54ffa0b9bfac3
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Program Files\Adobe\Acrobat DC\Acrobat\Acrobat.exe" "C:\Users\<USER>\Desktop\_Raindrop Roofing NW-protected.pdf"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Program Files\Adobe\Acrobat DC\Acrobat\Adobe Crash Processor.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: acroNGLLog.txt — C:\Users\<USER>\AppData\Local\Temp\acroNGLLog.txt
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: NGL — C:\Users\<USER>\AppData\Local\Temp\NGL\
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
Available reference checks returned no match, but at least one source was unavailable. This is not a clean result.
Signatures and behavior heuristics
A community signature or high-severity behavioral heuristic matched. Signatures identify known patterns; heuristics are strong leads but are not proof on their own.
The saved runtime evidence maps this activity to MITRE T1055 (Process Injection). The mapping supports possible process injection, but it does not prove the exact injection method or the operator's intent.
EvidenceC:\Windows\Explorer.EXESandbox observed process activity targeting LSASS (Windows credential store). Legitimate software has no business reading LSASS memory — this is Mimikatz-shape behaviour.
EvidenceC:\Windows\system32\lsass.exe
0 of 75 engines flagged this file
View all 75 engine results
PE structure
Not applicablePE structure analysis applies to Windows executable formats, not this file type.
How widely this file has been seen
Barely seen in the wild and first surfaced recently. That limits reputation evidence, but rarity alone is not proof of malware.
Fingerprint and provenance
- File name
- _Raindrop Roofing NW-protected.pdf
- Format
- Code signing
- Not applicable to this file type
- Size
- 98.4 KB
- Last analyzed
- Oct 7, 2026, 6:29 AM UTC
249e65c74e5be40302062f484e500abd7b823fdd93dc8b0070e54ffa0b9bfac3Safety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
We couldn't fully clear this file. Treat it with caution.
- Recovery step 01
Don't open it unless you're certain it came from a source you trust.
- Recovery step 02
Check where you got it — an unexpected attachment or a random download link is a red flag.
- Recovery step 03
If its origin cannot be confirmed, delete this file and use a fresh copy from a trusted source. Get a fresh copy from the original trusted source and verify its exact hash when possible.
- Recovery step 04
If you're still unsure, scan it again in a day or two — detections often catch up on newer files.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is _Raindrop Roofing NW-protected.pdf safe, or is it malware?
What is _Raindrop Roofing NW-protected.pdf?
How many antivirus engines detected _Raindrop Roofing NW-protected.pdf?
I already downloaded and opened _Raindrop Roofing NW-protected.pdf — what should I do?
How do I remove _Raindrop Roofing NW-protected.pdf?
What is the SHA-256 hash of _Raindrop Roofing NW-protected.pdf?
How up to date is this analysis of _Raindrop Roofing NW-protected.pdf?
Community
Member reviews and reports for this exact file hash.