Is BS EN 13501-1-2018.pdf safe?
No antivirus engine detected this PDF, but one sandbox trace mapped activity to credential access and process injection, warranting caution despite weak corroboration.
All 76 antivirus engines were silent, including 18 high-trust engines, and no complete contacted-host reputation result was available, child file, or external intelligence match was found. However, one sandbox trace produced credential-access and process-injection mappings, so the document should be handled cautiously until those behavioral alerts are independently reproduced.
27f1efcc0d10b12acb…83ec76305dbc23Recommended 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 76 antivirus engines were silent, including 18 high-trust engines, and no complete contacted-host reputation result was available, child file, or external intelligence match was found. However, one sandbox trace produced credential-access and process-injection mappings, so the document should be handled cautiously until those behavioral alerts are independently reproduced.
The static scan is strongly reassuring: 0 of 76 engines flagged the document, including no high-trust detections. One completed sandbox run did not issue a malicious conclusion, and its visible process activity largely involved Adobe Acrobat and standard Windows services. Nevertheless, that run mapped activity to T1003, T1055, and T1485, including a reported interaction with LSASS, which is too consequential to dismiss outright. The three observed domains received no malicious or suspicious cache matches, and no inspected child was identified as malware, although all ten child verdicts remain unknown. No YARA rule, known malware sample, or named family independently corroborates the behavioral warnings, making a behavioral false positive more likely than an established infection.
What We Detected
None of 76 antivirus engines flagged the PDF, and all 18 reporting high-trust engines were silent. Research intelligence also returned no YARA rule, known malware-sample match, or named threat family.
Threat Behavior
One completed sandbox run did not produce a malicious conclusion, but it mapped activity to T1003, T1055, and T1485. Two synthesis heuristics interpreted the trace as possible process injection and LSASS credential access. Those findings are concerning, yet they are not supported by engine detections, a malicious child, a known-bad host, or a second runtime observation. The visible process list primarily contains Adobe Acrobat and ordinary Windows components, so sandbox attribution or environmental noise is a plausible explanation.
What To Do Now
Keep endpoint protection enabled and open the document only in a fully updated PDF reader with scripting restricted where practical. For sensitive systems, obtain the document from an authoritative source and compare its SHA-256 value before use; otherwise, isolate it until another sandbox can reproduce or dismiss the LSASS and injection alerts.
Where this verdict could be wrong3 caveats
- MalwareTips.Synth.CredentialDumper reports activity targeting lsass.exe, which is a meaningful credential-access warning despite the absence of engine detections.
- MalwareTips.Synth.ProcessInjection maps activity to T1055, but its evidence contains only Explorer.EXE and does not establish the injection method.
- droppedChildren.inspected=10 found no malicious child, but all 10 child verdicts are unknown rather than confirmed benign.
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/76 antivirus engines detected the document.
- tier1Malicious=0 and tier1ReportedClean=18.
- behaviour.hasMaliciousSandboxVerdict=false.
- No cached malicious or suspicious match was found for the three contacted domains.
- No malicious child or external intelligence hit was identified.
- One sandbox trace mapped activity to T1003 credential access.
- Possible T1055 process injection was reported by a synthesis heuristic.
- The file has only one recorded submission from one source.
- All 10 inspected child hashes remain individually unknown.
Keep protection enabled and verify the PDF against a copy from an authoritative publisher before opening it. If verification is unavailable, use an isolated, fully patched PDF viewer and avoid handling it on a sensitive endpoint.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 76 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial3 of 7 contacted hosts were cross-checked; coverage is incomplete.
YARA
Complete2 signature or behavior rules matched.
External intel
Complete3 of 3 independent reference sources completed.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime flight recorder
Capture complete- 1isolated sandbox run
- 18MITRE ATT&CK techniques
- 15spawned processes
- 7network contacts
- 40filesystem & 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.
High concern: Manipulated how the operating system loads code, which can redirect execution.
Moderate concern: Communicated over a common application protocol; malware can use this for command-and-control.
Moderate concern: Communicates over the network in a non-standard way.
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
BS EN 13501-1-2018.pdf
27f1efcc0d10b12acbae8df5f8084b874e29b9ec7acad3c67e83ec76305dbc23
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Program Files\Adobe\Acrobat DC\Acrobat\Acrobat.exe" "C:\Users\<USER>\Desktop\BS EN 13501-1-2018.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
Network
Hosts contacted
- Contacted hostObserved
dns.google
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
acroipm2.adobe.com
Contact observed during runtime.
07Isolated runtime analysis - +1 more recorded observation in Analyst mode
7 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.
- dns.google
- acroipm2.adobe.com
- c.pki.goog
- 23.32.128.138
- 23.55.124.138
- 8.8.8.8
- 162.159.36.2
- HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\W32Time\Config\LastKnownGoodTime
- Software\Adobe\Acrobat Reader\DC\ExitSection\bLastExitNormal
- SOFTWARE\Adobe\Acrobat Reader\DC\DLLInjection\bBlockDLLInjection
- Software\Adobe\Acrobat Reader\DC\SessionManagement\bNormalExit
- cPathInfo\sDI
- cPathInfo\tDIText
- C:\Users\<USER>\AppData\Local\Temp\acroNGLLog.txt
- C:\Users\<USER>\AppData\Local\Temp\NGL\
- C:\Users\<USER>\AppData\Local\Temp\Tmp14DC.tmp
- C:\Users\<USER>\AppData\Local\Temp\A92pqdi1_187cb34_59w.tmp
- C:\Users\<USER>\AppData\Local\Temp\A9lhvw5s_187cb35_59w.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
- C:\Users\<USER>\AppData\Local\Adobe\Acrobat\DC\SOPHIA\Reader\Files\DC_READER_LAUNCH_CARD
- C:\Users\<USER>\AppData\Local\Adobe\Acrobat\DC\SOPHIA\Reader\Files\ACROBAT_READER_MASTER_SURFACEID
- Local\Acrobat Instance Mutex
- Global\_MSIExecute
- Global\MSILOG_c1163ed31dbc912GOL.ab921ISM_pmeT_lacoL_ataDppA_onurB_sresU_:C
- Global\AdobeCrashProcessorLocalLowLock
- Local\ZonesCacheCounterMutex
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- ad27039abac3252c3b39…37ede5Never scannednever seen before
- 15a93375882e244e6dc1…47b4d7Never scannednever seen before
- 81ff65efc4487853bdb4…7c8e06Never scannednever seen before
- c84f08075bb7d721b8c9…016252Never scannednever seen before
- 9d05d07fcbb91f79b3a0…a2f317Never scannednever seen before
- e3b0c44298fc1c149afb…52b855Never scannednever seen before
- aeb4d4eaf64889cb277f…d4a5dbNever scannednever seen before
- 7bb311d435e2baf05b40…be9d36Never scannednever seen before
- 4fd48574fedd2838ffc6…8a4c8bNever scannednever seen before
- 3acbd0b88ce84bac523f…169271Never 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 / 76engines 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 76 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: BS EN 13501-1-2018.pdf — 27f1efcc0d10b12acbae8df5f8084b874e29b9ec7acad3c67e83ec76305dbc23
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Program Files\Adobe\Acrobat DC\Acrobat\Acrobat.exe" "C:\Users\<USER>\Desktop\BS EN 13501-1-2018.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 - 09
Contacted host: dns.google — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: acroipm2.adobe.com — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
MalwareBazaar, YARAify, and CIRCL hashlookup completed and returned no entries for this hash.
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 76 engines flagged this file
View all 76 engine results
PE structure
Not applicablePE structure analysis applies to Windows executable formats, not this file type.
How widely this file has been seen
Rarely uploaded, but has been around for a while. Often niche legitimate software or old internal tooling; not a strong malware signal on its own.
Fingerprint and provenance
- File name
- BS EN 13501-1-2018.pdf
- Format
- Code signing
- Not applicable to this file type
- Size
- 988.7 KB
- Last analyzed
- Sep 25, 2026, 12:27 PM UTC
27f1efcc0d10b12acbae8df5f8084b874e29b9ec7acad3c67e83ec76305dbc23Safety & 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 BS EN 13501-1-2018.pdf safe, or is it malware?
What is BS EN 13501-1-2018.pdf?
How many antivirus engines detected BS EN 13501-1-2018.pdf?
What should I do if I already opened BS EN 13501-1-2018.pdf?
How do I remove BS EN 13501-1-2018.pdf?
What is the SHA-256 hash of BS EN 13501-1-2018.pdf?
How up to date is this analysis of BS EN 13501-1-2018.pdf?
Community
Member reviews and reports for this exact file hash.