Is portable.exe safe?
Unsigned portable executable with low-trust ML flag and sandbox evidence of process injection and LSASS access.
One low-trust engine flagged the file; 74 others remained silent. Sandbox recorded process-injection and LSASS activity, yet no tier-1 consensus, no malicious children, and no external-intel hits exist.
a7eab90137b4498775…18c5aa13dd335fRecommended next actions
Before running
Do not run it until the source and publisher can be verified independently.
If you already ran it
Stop using it, scan the device, and watch for unexpected behavior or security alerts. Get a fresh copy from the developer's official site or an official app store.
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.
One low-trust engine flagged the file; 74 others remained silent. Sandbox recorded process-injection and LSASS activity, yet no tier-1 consensus, no malicious children, and no external-intel hits exist.
The single low-trust detection and unsigned status keep the file out of the safe band. Offensive MITRE techniques and direct-IP traffic raise concern, but the absence of tier-1 corroboration, malicious dropped children, and external-intel hits prevents a malicious verdict. Medium prevalence and portable filename provide limited context but do not resolve the mixed signals.
What We Detected
75 engines scanned the 14 MB Win32 executable; only Trapmine returned a malicious label. No tier-1 engine flagged the sample. The file is unsigned and carries no code-signing history.
Threat Behavior
Sandbox execution showed process-injection (T1055), data destruction (T1485), and defense-evasion (T1562.001) techniques, plus direct IP connections to 150.171.28.11 and 162.159.36.2. LSASS memory access was observed, but no malicious child files were dropped and no sandbox verdict labeled the run malicious.
What To Do Now
Do not run the file on production systems. Keep endpoint protection enabled. If the file is required, execute it only in an isolated virtual machine and monitor for unexpected outbound traffic or credential-store access.
Where this verdict could be wrong1 caveat
- Sandbox observed LSASS access and direct-IP traffic, but hasMaliciousSandboxVerdict=false and no malicious child files or external-intel hits corroborate maliciousness.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Zero tier-1 malicious detections
- No malicious dropped children
- Medium prevalence across 54 sources
- Unsigned executable
- Sandbox observed LSASS access
- Direct-IP network traffic without domain context
- Process-injection and defense-evasion techniques recorded
Treat the file as untrusted; run only in an isolated environment with active monitoring until additional reputable detections or a trusted publisher signature appear.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete1 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial2 runtime contacts were observed without a completed reputation cross-check.
YARA
Complete3 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
- 18MITRE ATT&CK techniques
- 15spawned processes
- 2network contacts
- 36filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Injected code into another process, a technique that can conceal execution.
High concern: Used an input-capture technique that can record credentials or keystrokes.
High concern: Attempted to impair or bypass security controls.
High concern: Manipulated how the operating system loads code, which can redirect execution.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Moderate concern: Runs hidden system commands (script or shell).
Moderate concern: Communicated over a common application protocol; malware can use this for command-and-control.
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
portable.exe
a7eab90137b449877579d066372df0c5e699f22c06d8b5a6be18c5aa13dd335f
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\portable.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Program Files (x86)\Microsoft\EdgeWebView\Application\122.0.2365.92\msedgewebview2.exe" --embedded-browser-webview=1 --webview-exe-name=portable.exe --webview-exe-version=8.23.4 --user-data-dir="C:\Users\<USER>\AppData\Local\net.wearedevs.portable\EBWebView" --noerrdialogs --embedded-browser-webview-dpi-awareness=2 --edge-webview-custom-scheme --autoplay-policy=no-user-gesture-required --disable-features=msWebOOUI,msPdfOOUI,msSmartScreenProtection --enable-features=MojoIpcz --lang=en-US --accept-lang=en-US --mojo-named-platform-channel-pipe=3544.5988.3937382862460046120
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
throttle_store.dat
C:\Users\<USER>\AppData\Local\net.wearedevs.portable\EBWebView\Crashpad\throttle_store.dat
04Isolated runtime analysis - Written fileObserved
settings.dat
C:\Users\<USER>\AppData\Local\net.wearedevs.portable\EBWebView\Crashpad\settings.dat
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
150.171.28.11
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
162.159.36.2
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.
- 150.171.28.11
- 162.159.36.2
- C:\Users\<USER>\AppData\Local\net.wearedevs.portable\EBWebView\Crashpad\throttle_store.dat
- C:\Users\<USER>\AppData\Local\net.wearedevs.portable\EBWebView\Crashpad\settings.dat
- C:\Users\<USER>\AppData\Local\net.wearedevs.portable\EBWebView\BrowserMetrics\BrowserMetrics-6A9EDD29-13E0.pma
- C:\Users\<USER>\AppData\Local\net.wearedevs.portable\EBWebView\lockfile
- C:\Users\<USER>\AppData\Local\net.wearedevs.portable\EBWebView\Variations
- C:\Users\<USER>\AppData\Local\net.wearedevs.portable\EBWebView\BrowserMetrics-spare.pma
- C:\Users\<USER>\AppData\Local\net.wearedevs.portable\EBWebView\bbd18b2c-514c-45ac-89ee-9c8fd8e57393.tmp
- C:\Users\<USER>\AppData\Local\net.wearedevs.portable\EBWebView\Default\Code Cache\js\index-dir\temp-index
- C:\Users\<USER>\AppData\Local\net.wearedevs.portable\EBWebView\Default\Extension Rules\000001.dbtmp
- C:\Users\<USER>\AppData\Local\net.wearedevs.portable\EBWebView\Default\shared_proto_db\metadata\000001.dbtmp
- Local\ChromeProcessSingletonStartup!
- __OMADM_NAMED_MUTEX__
- Global\OneSettingQueryMutex+compat+encapsulation
- \Sessions\1\BaseNamedObjects\DBWinMutex
- \Sessions\1\BaseNamedObjects\Local\ChromeProcessSingletonStartup!
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- fbcfe23a2ecb82b7100c…dc0f2dNever scannednever seen before
- 58623bbe02c34662b6f4…388d74Never scannednever seen before
- 2ed066dbff47e4415f8d…07793bNever scannednever seen before
- 3c979effebd863906e90…910ecbNever scannednever seen before
- 8481c4ef42409d179766…3229ceNever scannednever seen before
- a0c9abae18599f0a65fc…e38e87Never scannednever seen before
- b1e963d702392fb72247…c0cdecNever scannednever seen before
- 5dfc321417fc31359f23…4a2026Never scannednever seen before
- 0f1bad70c7bd1e0a6956…780443Never scannednever seen before
- 1a6a2e41dfb8e9843ac8…6aab26Never 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.
- 3rule hits recorded
- 1 / 75engines flagged
- 54sources 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
1 of 75 antivirus engines flagged the file, including Trapmine.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 58 times from 54 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: portable.exe — a7eab90137b449877579d066372df0c5e699f22c06d8b5a6be18c5aa13dd335f
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\portable.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Program Files (x86)\Microsoft\EdgeWebView\Application\122.0.2365.92\msedgewebview2.exe" --embedded-browser-webview=1 --webview-exe-name=portable.exe --webview-exe-version=8.23.4 --user-data-dir="C:\Users\<USER>\AppData\Local\net.wearedevs.portable\EBWebView" --noerrdialogs --embedded-browser-webview-dpi-awareness=2 --edge-webview-custom-scheme --autoplay-policy=no-user-gesture-required --disable-features=msWebOOUI,msPdfOOUI,msSmartScreenProtection --enable-features=MojoIpcz --lang=en-US --accept-lang=en-US --mojo-named-platform-channel-pipe=3544.5988.3937382862460046120
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: throttle_store.dat — C:\Users\<USER>\AppData\Local\net.wearedevs.portable\EBWebView\Crashpad\throttle_store.dat
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: settings.dat — C:\Users\<USER>\AppData\Local\net.wearedevs.portable\EBWebView\Crashpad\settings.dat
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 150.171.28.11 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 162.159.36.2 — Contact observed during runtime.
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\System32\svchost.exe -k NetworkService -pSandbox 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.exeThe sample contacted an external IP address directly and no application domain was recorded. Direct-IP traffic also occurs in legitimate installers and infrastructure, so this is supporting context only and requires corroboration from host reputation and other runtime evidence.
Evidence150.171.28.11 · 162.159.36.2
1 of 75 engines flagged this file
View all 75 engine results
Section entropy & packers
No high-entropy executable section or known packer signature was detected. Data and resource sections can still have high entropy without indicating packed code.
How widely this file has been seen
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- portable.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 13.6 MB
- Last analyzed
- Sep 7, 2026, 5:39 PM UTC
a7eab90137b449877579d066372df0c5e699f22c06d8b5a6be18c5aa13dd335fSafety & 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 run 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 developer's official site or an official app store.
- 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 portable.exe safe, or is it malware?
What is portable.exe?
How many antivirus engines detected portable.exe?
I already downloaded and ran portable.exe — what should I do?
How do I remove portable.exe?
What is the SHA-256 hash of portable.exe?
How up to date is this analysis of portable.exe?
Community
Member reviews and reports for this exact file hash.