Is CPPWrapper.exe safe?
No antivirus engine detected this unsigned executable, but sandbox indicators involving process injection, defense impairment, and LSASS access warrant caution and further validation.
All 75 antivirus engines avoided flagging the file, including 17 tier-1 products, and the completed sandbox did not issue a malware finding. However, the unsigned executable produced T1055 and T1562.001 indicators and activity involving LSASS, so it should not be trusted solely from the clean engine result.
cac8282a040a5fe7fe…917a481f806fd9Recommended 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.
All 75 antivirus engines avoided flagging the file, including 17 tier-1 products, and the completed sandbox did not issue a malware finding. However, the unsigned executable produced T1055 and T1562.001 indicators and activity involving LSASS, so it should not be trusted solely from the clean engine result.
The strongest reassuring evidence is that 0 of 75 engines detected the sample, with all 17 reporting tier-1 engines returning no detection. One completed sandbox also recorded a clean disposition, and the inspected child was not identified as malicious. Against that, runtime evidence mapped activity to process injection and impairment of defenses, while an additional heuristic associated process activity with LSASS. The executable is unsigned and only recently observed, leaving no verified publisher identity or mature history to explain those behaviors. Two domain hosts had no cached threat findings, but the observed IP contact was not demonstrably covered, so no complete host-reputation conclusion is available.
What We Detected
No detections were reported by 75 antivirus engines, including 17 tier-1 products. The Win32 executable is unsigned, has no established signer history, and was first observed three days before this analysis.
Threat Behavior
One completed sandbox run recorded indicators mapped to MITRE T1055 for process injection and T1562.001 for impairment of defenses. Saved process evidence also involved lsass.exe, producing a credential-dumper-shaped heuristic, although the sandbox itself did not issue a malware finding. No persistence indicators were recorded, and the inspected dropped child was not identified as malicious; its individual disposition remains unknown. The two inspected domain hosts had no cached malicious or suspicious findings, but complete reputation coverage for every observed network contact is not demonstrated.
What To Do Now
Keep endpoint protection enabled and avoid running the file on a production system until its source and purpose are verified. If execution is necessary for research, use an isolated disposable environment and investigate whether the LSASS and injection-related activity is expected for the software.
Where this verdict could be wrong4 caveats
- The complete 0/75 detection result, including 17 clean tier-1 reports, weighs strongly against the concerning runtime indicators.
- The sandbox's saved verdict was clean, and no persistenceIndicators were recorded.
- The sample is newly observed but already has prevalence.uniqueSources=159 and prevalence.timesSubmitted=176, which is broader distribution than a one-off payload.
- contactedHosts has no malicious or suspicious findings for its two inspected domain hosts, but the observed IP address is not demonstrably covered.
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 detection
- All 17 reporting tier-1 engines returned no detection
- behaviour.hasMaliciousSandboxVerdict=false
- droppedChildren.hasMaliciousChild=false
- peAnalysis.likelyPacked=false and peAnalysis.highEntropyCode=false
- Unsigned Win32 executable with no verified publisher identity
- MITRE T1055 process-injection indicator
- MITRE T1562.001 defense-impairment indicator
- Sandbox process evidence involving lsass.exe
- Only three days of observed history
- Incomplete reputation coverage across all observed network contacts
Do not deploy or execute this file on a trusted machine until its origin is verified and the LSASS and injection indicators are explained. Keep antivirus and endpoint protection enabled during any further testing.
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
Partial2 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
- 10MITRE ATT&CK techniques
- 9spawned processes
- 3network contacts
- 1filesystem & 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: 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: Communicated over a common application protocol; malware can use this for command-and-control.
Moderate concern: Checks which security software you have installed.
Note: Reads your Windows user-account details.
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
CPPWrapper.exe
cac8282a040a5fe7fe2c5aaad1481cb2f0e739f93a87010f90917a481f806fd9
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\SuperPSX-EA.SPORTS.UFC.4-CUSA14209-v1.00-7.5_48091.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\system32\services.exe
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
1zip-guid.cache
C:\Users\<USER>\AppData\Local\Temp\1zip-guid.cache
04Isolated runtime analysis - Dropped fileDerived
8e69462faf2df2fdf279ab510dcb3f53d6ee5782c88e4fe8197c835c771442df
No child-file verdict was available.
05Dropped-file analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
a1672.dscr.akamai.net
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
assets.msn.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.
- a1672.dscr.akamai.net
- assets.msn.com
- 162.159.36.2
- C:\Users\<USER>\AppData\Local\Temp\1zip-guid.cache
Files this sample writes at runtime
This file drops 1 child at runtime. None are currently flagged malicious in our cache.
- 8e69462faf2df2fdf279…1442dfNever 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
- 159sources 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 176 times from 159 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: CPPWrapper.exe — cac8282a040a5fe7fe2c5aaad1481cb2f0e739f93a87010f90917a481f806fd9
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\SuperPSX-EA.SPORTS.UFC.4-CUSA14209-v1.00-7.5_48091.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\system32\services.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: 1zip-guid.cache — C:\Users\<USER>\AppData\Local\Temp\1zip-guid.cache
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
Dropped file: 8e69462faf2df2fdf279ab510dcb3f53d6ee5782c88e4fe8197c835c771442df — No child-file verdict was available.
ProvenanceDerivedSourceDropped-file analysisObserved at - 09
Contacted host: a1672.dscr.akamai.net — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: assets.msn.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\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.exe
0 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
- CPPWrapper.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 26.4 MB
- Last analyzed
- Sep 27, 2026, 4:55 PM UTC
cac8282a040a5fe7fe2c5aaad1481cb2f0e739f93a87010f90917a481f806fd9Safety & 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 CPPWrapper.exe safe, or is it malware?
What is CPPWrapper.exe?
How many antivirus engines detected CPPWrapper.exe?
I already downloaded and ran CPPWrapper.exe — what should I do?
How do I remove CPPWrapper.exe?
What is the SHA-256 hash of CPPWrapper.exe?
How up to date is this analysis of CPPWrapper.exe?
Community
Member reviews and reports for this exact file hash.