Is Painter_cv_Onyedikachi_Orjiako.pdf safe?
No antivirus engine detected the PDF, but one sandbox produced uncorroborated credential-access, injection, and destructive-technique mappings that warrant cautious handling.
The PDF drew no detections from 75 antivirus engines, and the completed sandbox did not issue a malware disposition. However, its telemetry mapped activity to credential access, process injection, and file destruction, while network and child-artifact checks remain incomplete, so opening it outside a protected viewer is not advisable.
38fd017f9ed88ffe86…0f44a95d7fdf38Recommended 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.
The PDF drew no detections from 75 antivirus engines, and the completed sandbox did not issue a malware disposition. However, its telemetry mapped activity to credential access, process injection, and file destruction, while network and child-artifact checks remain incomplete, so opening it outside a protected viewer is not advisable.
No antivirus engine flagged the PDF, including the tier-1 engines that completed analysis. One completed sandbox produced no malware disposition and showed mostly Adobe Acrobat processes, but its telemetry mapped activity to T1003, T1055, and T1485. Those mappings are concerning, yet the recorded evidence does not clearly attribute the activity to the document rather than the viewer or sandbox environment. No inspected child was identified as malware, although all ten child verdicts remain unresolved. Independent researcher intelligence produced no matches, and the host-reputation check covered only one of three observed contacts. The result is therefore mixed, with substantial indications that the behavioral alerts may be false positives but insufficient evidence to dismiss them completely.
What We Detected
The PDF received 0 detections from 75 antivirus engines, with engines.tier1Malicious=0 and 11 tier-1 engines reporting no detection. External checks also returned externalIntel.yaraify.ruleCount=0, externalIntel.circl.hit=false, and externalIntel.malwareBazaar.hit=false.
Threat Behavior
One completed sandbox did not issue a malware disposition and recorded processes largely associated with Adobe Acrobat. However, the telemetry mapped activity to T1003, T1055, and T1485, and triggered the ProcessInjection and CredentialDumper heuristics. These are meaningful risk indicators, but the saved evidence links them only to generic system processes and does not conclusively show that the PDF initiated them. Ten child artifacts were inspected without an identified malicious child, though every child verdict remains unknown. The host-reputation check inspected only one of three observed contacts, so a complete network-reputation result is unavailable.
What To Do Now
Do not open the document on a sensitive or production system unless its sender and purpose are independently verified. Keep endpoint protection enabled, use an updated sandboxed PDF viewer, and avoid enabling embedded content or following links until the behavioral alerts are resolved.
Where this verdict could be wrong3 caveats
- The T1003, T1055, and T1485 mappings are offensive-behavior signals and cannot be dismissed solely because 0/75 engines detected the file.
- contactedHosts.inspected=1 does not cover all three distinct contacts in behaviour.contactedDomains and behaviour.contactedIps, leaving network reputation only partially checked.
- All 10 inspected child files have unknown verdicts, so droppedChildren.hasMaliciousChild=false does not establish that every artifact is 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/75 antivirus engines reported a malicious or suspicious result.
- engines.tier1Malicious=0 and engines.tier1ReportedClean=11.
- behaviour.hasMaliciousSandboxVerdict=false.
- droppedChildren.hasMaliciousChild=false.
- YARAify, CIRCL, and MalwareBazaar returned no sample match.
- behaviour.offensiveTechniques includes T1003 credential access.
- behaviour.offensiveTechniques includes T1055 process injection.
- behaviour.offensiveTechniques includes T1485 data destruction.
- MalwareTips.Synth.CredentialDumper fired on activity involving lsass.exe.
- Host-reputation coverage inspected only 1 of 3 distinct observed contacts.
- All 10 inspected child artifacts retain unknown verdicts.
Verify the sender and obtain a fresh copy through a trusted channel before opening it. Keep endpoint protection enabled and use an updated, sandboxed PDF viewer on a non-sensitive system if inspection is necessary.
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
Partial1 of 3 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
- 12MITRE ATT&CK techniques
- 14spawned processes
- 3network contacts
- 35filesystem & 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: Communicated over a common application protocol; malware can use this for command-and-control.
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
Painter_cv_Onyedikachi_Orjiako.pdf
38fd017f9ed88ffe86661bb040583e68416b43fc13aebc20de0f44a95d7fdf38
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Program Files\Adobe\Acrobat DC\Acrobat\Acrobat.exe" "C:\Users\<USER>\Desktop\Painter_cv_Onyedikachi_Orjiako.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
acroipm2.adobe.com
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
8.8.8.8
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.
- acroipm2.adobe.com
- 8.8.8.8
- 162.159.36.2
- 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
- cPathInfo\aFS
- C:\Users\<USER>\AppData\Local\Temp\acroNGLLog.txt
- C:\Users\<USER>\AppData\Local\Temp\NGL\
- C:\Users\<USER>\AppData\Local\Temp\TmpCDC.tmp
- C:\Users\<USER>\AppData\Local\Temp\TmpEF0.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
- 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
- Global\_MSIExecute
- Global\MSILOG_fe6005581dd2ed8GOL.31321ISM_pmeT_lacoL_ataDppA_onurB_sresU_:C
- \Sessions\1\BaseNamedObjects\{100184D2-BDC3-477a-B8D3-65548B67914C}_1696
- \Sessions\1\BaseNamedObjects\Local\{100184D2-BDC3-477a-B8D3-65548B67914C}_5804
- \Sessions\1\BaseNamedObjects\Local\Acrobat Instance Mutex
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- eacad3e01b8b0a44ac03…df796dNever scannednever seen before
- 513fb5d3b4195ab59af2…64de2eNever scannednever seen before
- ad27039abac3252c3b39…37ede5Never scannednever seen before
- e0f228d85e6882b35c2c…068306Never scannednever seen before
- 81ff65efc4487853bdb4…7c8e06Never scannednever seen before
- a55b8e4405e220530dcf…20fc40Never scannednever seen before
- 092f8866aa77ac8bc155…7eb699Never scannednever seen before
- e3b0c44298fc1c149afb…52b855Never scannednever seen before
- a5c6d4dbae668479ccb9…11631bNever scannednever seen before
- 4df98d996551189e28df…fe1f0dNever 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: Painter_cv_Onyedikachi_Orjiako.pdf — 38fd017f9ed88ffe86661bb040583e68416b43fc13aebc20de0f44a95d7fdf38
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Program Files\Adobe\Acrobat DC\Acrobat\Acrobat.exe" "C:\Users\<USER>\Desktop\Painter_cv_Onyedikachi_Orjiako.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: acroipm2.adobe.com — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 8.8.8.8 — 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 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
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- Painter_cv_Onyedikachi_Orjiako.pdf
- Format
- Code signing
- Not applicable to this file type
- Size
- 802.6 KB
- Last analyzed
- Sep 25, 2026, 5:33 AM UTC
38fd017f9ed88ffe86661bb040583e68416b43fc13aebc20de0f44a95d7fdf38Safety & 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 Painter_cv_Onyedikachi_Orjiako.pdf safe, or is it malware?
What is Painter_cv_Onyedikachi_Orjiako.pdf?
How many antivirus engines detected Painter_cv_Onyedikachi_Orjiako.pdf?
What should I do if I already opened Painter_cv_Onyedikachi_Orjiako.pdf?
How do I remove Painter_cv_Onyedikachi_Orjiako.pdf?
What is the SHA-256 hash of Painter_cv_Onyedikachi_Orjiako.pdf?
How up to date is this analysis of Painter_cv_Onyedikachi_Orjiako.pdf?
Community
Member reviews and reports for this exact file hash.