Is portable.exe safe?
The unsigned executable shows process-injection, credential-access, destruction, and protection-impairment indicators, but sparse generic detections and one clean sandbox result prevent firm family attribution.
Three of 75 engines flagged the executable, including Kaspersky, while runtime evidence mapped activity to process injection, LSASS access, data destruction, ransomware-style impact, and protection impairment. The labels lack a consistent family, one sandbox returned clean, and the two contacted IP addresses were not reputation-checked, leaving materially conflicting evidence.
1468e3d24157ea45ea…dd4b084acc958dRecommended 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.
Three of 75 engines flagged the executable, including Kaspersky, while runtime evidence mapped activity to process injection, LSASS access, data destruction, ransomware-style impact, and protection impairment. The labels lack a consistent family, one sandbox returned clean, and the two contacted IP addresses were not reputation-checked, leaving materially conflicting evidence.
The detection count is limited to 3 of 75 engines, but one is Kaspersky and the file is an unsigned executable without publisher history. More importantly, the completed sandbox observation produced mappings to T1055, T1485, T1486, and T1562.001, with a separate heuristic identifying LSASS-targeting activity. Those behaviors are difficult to dismiss as ordinary portable-application activity, although the saved evidence does not prove each technique's exact implementation or intent. Counter-signals include a clean sandbox verdict, no identified malicious child among ten inspected hashes, and no corroborating external-intelligence hit. Reputation coverage is incomplete for the two observed IP addresses, and the generic engine labels do not establish a malware family. Taken together, the evidence supports containment and further investigation rather than routine execution.
What We Detected
Three of 75 antivirus engines flagged the executable. Kaspersky used the generic label DangerousObject, Malwarebytes identified RiskWare.Agent, and Trapmine supplied a machine-learning detection; there is no strong tier-1 family consensus. The file is unsigned and has no established publisher history.
Threat Behavior
One completed sandbox observation mapped activity to T1055 process injection, T1485 data destruction, T1486 impact through data encryption, and T1562.001 impairment of defenses. A separate heuristic reports activity targeting LSASS, which may indicate credential-access behavior. The sample also contacted 150.171.28.11 and 162.159.36.2 directly, but no complete host-reputation result is available, so those contacts cannot be characterized as benign or malicious. One sandbox returned a clean verdict, and none of ten inspected dropped hashes was identified as malicious, although all ten child verdicts remain unknown.
What To Do Now
Do not run the executable on a production or personal system until its origin and purpose are independently verified. Keep endpoint protection enabled, quarantine the file, and investigate any system where it already ran for LSASS access, injected processes, altered security settings, and unexpected file encryption or deletion.
Where this verdict could be wrong5 caveats
- Only 3/75 engines detected the sample, and 16 of 17 reporting tier-1 engines did not flag it.
- behaviour.sandboxVerdicts contains one clean result and behaviour.hasMaliciousSandboxVerdict=false.
- droppedChildren.hasMaliciousChild=false, although all 10 inspected children retain unknown verdicts.
- externalIntel.yaraify.ruleCount=0, externalIntel.malwareBazaar.hit=false, and externalIntel.circl.hit=false provide no researcher-curated corroboration.
- prevalence records 205 submitters and 223 submissions, so the sample is not isolated despite being recently observed.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- 16 of 17 reporting tier-1 engines did not flag the sample
- One completed sandbox returned a clean verdict
- No malicious child was identified among 10 inspected dropped hashes
- No CIRCL, MalwareBazaar, or YARAify corroboration was found
- PE analysis found no likely packing or high-entropy code
- Unsigned Win32 executable with no established signer history
- Runtime mapping to T1055 process injection
- Heuristic evidence of LSASS-targeting activity
- Runtime mappings to T1485 and T1486 destructive or encryption impact
- Runtime mapping to T1562.001 impairment of defenses
- Direct connections to two IP addresses without completed reputation coverage
Quarantine the file and obtain it again only from a verified official source before considering execution. If it already ran, keep protection enabled and perform a full endpoint scan plus targeted review for credential access, process injection, defense changes, and file damage.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete3 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
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
- 21MITRE 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: Encrypted files or data, behaviour commonly associated with ransomware.
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).
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
1468e3d24157ea45eabadcb2cde1d2e39906c28d5874b34057dd4b084acc958d
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.25.0 --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=2088.5368.4724085721430141528
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
- HKEY_CURRENT_USER\SOFTWARE\Microsoft\EdgeUpdate\ClientState\{F3017226-FE2A-4295-8BDF-00C3A9A7E4C5}\dr
- HKEY_CURRENT_USER\SOFTWARE\Microsoft\EdgeWebView\StabilityMetrics\user_experience_metrics.stability.exited_cleanly
- HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\EdgeUpdate\ClientStateMedium\{F3017226-FE2A-4295-8BDF-00C3A9A7E4C5}\usagestats
- HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\EdgeUpdate\ClientStateMedium\{F3017226-FE2A-4295-8BDF-00C3A9A7E4C5}\urlstats
- HKEY_CURRENT_USER\SOFTWARE\Microsoft\EdgeWebView\PreferenceMACs\Default\media.cdm.origin_data
- HKEY_CURRENT_USER\SOFTWARE\Microsoft\EdgeWebView\PreferenceMACs\Default\media.storage_id_salt
- 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-6AB9C3F9-D24.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\Default\Code Cache\wasm\index-dir\the-real-index
- C:\Users\<USER>\AppData\Local\net.wearedevs.portable\EBWebView\Default\Code Cache\js\index-dir\the-real-index
- 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\Code Cache\wasm\index-dir\temp-index
- 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
- 40c87634bd0ebfebf4a4…6d958fNever scannednever seen before
- a0c9abae18599f0a65fc…e38e87Never scannednever seen before
- b1e963d702392fb72247…c0cdecNever scannednever seen before
- 5dfc321417fc31359f23…4a2026Never scannednever seen before
- 0f1bad70c7bd1e0a6956…780443Never scannednever seen before
- 4f53cda18c2baa0c0354…02b945Never scannednever seen before
- deba77bc71479c2e98a7…e1c573Never scannednever seen before
- 0628922305d2478ba75a…e28107Never scannednever seen before
- 79b107307408e5ad9a14…25b3b1Never 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
- 3 / 75engines flagged
- 205sources 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
3 of 75 antivirus engines flagged the file, including Kaspersky and Malwarebytes.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 223 times from 205 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: portable.exe — 1468e3d24157ea45eabadcb2cde1d2e39906c28d5874b34057dd4b084acc958d
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.25.0 --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=2088.5368.4724085721430141528
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.
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\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
3 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
Lots of people are uploading this but it's recent — typical of newly-released legitimate software. Low prior for malware.
Fingerprint and provenance
- File name
- portable.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 13.6 MB
- Last analyzed
- Sep 29, 2026, 7:43 PM UTC
1468e3d24157ea45eabadcb2cde1d2e39906c28d5874b34057dd4b084acc958dSafety & 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.