Is ncNeL7MAc.exe safe?
Twenty-one of 75 engines flagged this newly observed executable, with multiple leading engines naming OfferCore and the Infivora signer showing a consistently harmful history.
Multiple independent engines identify this executable as an OfferCore bundler or unwanted downloader, including six high-trust detections. Its verified Infivora signature does not reduce concern because all seven historical samples from that signer were harmful, while runtime evidence includes process-injection mapping and LSASS-related activity.
c37ad5bdbb44f1af0b…006916771896fdRecommended next actions
Before running
Do not run it. Delete this file from the device, then empty the Recycle Bin or Trash.
If you already ran it
Disconnect from the internet, start a full or offline antivirus scan, then secure important accounts from a clean device.
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.
Multiple independent engines identify this executable as an OfferCore bundler or unwanted downloader, including six high-trust detections. Its verified Infivora signature does not reduce concern because all seven historical samples from that signer were harmful, while runtime evidence includes process-injection mapping and LSASS-related activity.
The detection volume is substantial: 21 of 75 engines flagged the sample, including six high-trust engines. BitDefender, Emsisoft, GData, ESET-NOD32, and Microsoft converge on OfferCore or closely related bundler behavior, although the formal tier-one family consensus is not strong. The verified Infivora signature is adverse rather than reassuring because its recorded history is 7/7 malicious samples and it is not a trusted publisher. Runtime evidence maps activity to T1055 and records LSASS involvement, adding concern beyond PUA labels alone. A prior file sharing both this imphash and signer was also identified as OfferCore, strongly reinforcing the family attribution. The clean sandbox label, fully checked contacted host, and unflagged dropped child are meaningful counter-signals but do not outweigh the engine, signer-history, and runtime evidence.
What We Detected
Twenty-one of 75 antivirus engines flagged the executable, including six high-trust detections. BitDefender, Emsisoft, GData, ESET-NOD32, and Microsoft identify OfferCore or an OfferCore bundler, while DrWeb reports InstallCore and Kaspersky reports a related unwanted downloader pattern. The file is signed by Infivora, but that publisher is not on the trusted list and its recorded history contains 7/7 harmful samples.
Threat Behavior
Completed runtime observation mapped activity to MITRE T1055, which concerns process injection, and saved evidence also involved the Windows LSASS process. The sample contacted one CloudFront domain; the host-reputation check covered the observed host and found no cached malicious or suspicious classification. One dropped file was inspected without a harmful verdict, and the sandbox's overall label was clean, but these counter-signals do not negate the more specific runtime indicators.
What To Do Now
Do not run or install this executable. Quarantine or delete it with endpoint protection kept enabled; if it already ran, perform a full system scan and review installed applications, browser settings, startup entries, and account security for unwanted changes.
Where this verdict could be wrong4 caveats
- signing.verified=true for 'Infivora', although signing.signerStats shows 7/7 malicious historical samples and trustedPublisher.matched=false.
- behaviour.hasMaliciousSandboxVerdict=false; the single sandbox labeled the run clean despite recording T1055 and LSASS-related activity.
- contactedHosts inspected the one distinct CloudFront host and found no known-malicious or suspicious host, while droppedChildren.hasMaliciousChild=false.
- externalIntel.yaraify.ruleCount=0 and externalIntel.circl.hit=false provide no independent researcher-intelligence corroboration.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- The Infivora digital signature verifies cryptographically
- The fully inspected contacted host had no cached malicious or suspicious classification
- The inspected dropped child had no harmful verdict
- The single sandbox's overall label was clean
- No packing or high-entropy code was detected
- 21/75 antivirus detections
- Six high-trust engine detections
- Repeated OfferCore or bundler attribution
- Infivora signer history is 7/7 malicious
- MITRE T1055 process-injection evidence
- Saved runtime evidence involving LSASS
Keep endpoint protection enabled and quarantine or remove the file rather than launching it. If it already executed, run a full scan and inspect the system for unwanted software and account compromise.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete21 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial1 of 2 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
- 11MITRE ATT&CK techniques
- 10spawned processes
- 4network contacts
- 3filesystem & 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.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Moderate concern: Removed execution artefacts or logs, which can conceal activity.
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.
Note: Loads extra code modules while running.
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.
Threat context
How bundlers & adware work
This is a bundler — a real-looking installer that hides extra software inside. When you run it, it quietly installs things you never asked for: ad injectors, browser toolbars, fake 'PC cleaner' apps, or even more bundlers. The people behind it get paid for every unwanted app they sneak on.
Bottom line:It's not usually built to destroy files, but it slows your PC, floods it with ads, and can be a real pain to fully remove.
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
ncNeL7MAc.exe
c37ad5bdbb44f1af0b1fc7223c07fcee1a9d71d13a326bde5c006916771896fd
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\rRRyCKN1A.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Users\<USER>\AppData\Local\Temp\is-946H8ZK1OP.tmp\rRRyCKN1A.tmp" /SL5="$5003E,14880881,843264,C:\Users\<USER>\Desktop\rRRyCKN1A.exe"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
rRRyCKN1A.tmp
C:\Users\<USER>\AppData\Local\Temp\is-946H8ZK1OP.tmp\rRRyCKN1A.tmp
04Isolated runtime analysis - Written fileObserved
is-O4FAIAFU2I.tmp
C:\Users\user\AppData\Local\Temp\is-O4FAIAFU2I.tmp
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
d2cxzkcwhivupa.cloudfront.net
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
108.156.248.214
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.
- d2cxzkcwhivupa.cloudfront.net
- 108.156.248.214
- https://d2cxzkcwhivupa.cloudfront.net/o
- https://d2cxzkcwhivupa.cloudfront.net/zbd
- C:\Users\<USER>\AppData\Local\Temp\is-946H8ZK1OP.tmp\rRRyCKN1A.tmp
- C:\Users\user\AppData\Local\Temp\is-O4FAIAFU2I.tmp
- C:\Users\user\AppData\Local\Temp\is-O4FAIAFU2I.tmp\rRRyCKN1A.tmp
Files this sample writes at runtime
This file drops 1 child at runtime. None are currently flagged malicious in our cache.
- dc8c86bf2ce73f88cf48…ecf0f3Never 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
- 21 / 75engines flagged
- 2sources 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
21 of 75 antivirus engines flagged the file, including AhnLab-V3 and ALYac.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The file has a valid code signature from Infivora.
ProvenanceObservedSourceCode-signing metadataObserved at - 04
Scanned file: ncNeL7MAc.exe — c37ad5bdbb44f1af0b1fc7223c07fcee1a9d71d13a326bde5c006916771896fd
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\rRRyCKN1A.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Users\<USER>\AppData\Local\Temp\is-946H8ZK1OP.tmp\rRRyCKN1A.tmp" /SL5="$5003E,14880881,843264,C:\Users\<USER>\Desktop\rRRyCKN1A.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: rRRyCKN1A.tmp — C:\Users\<USER>\AppData\Local\Temp\is-946H8ZK1OP.tmp\rRRyCKN1A.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: is-O4FAIAFU2I.tmp — C:\Users\user\AppData\Local\Temp\is-O4FAIAFU2I.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: d2cxzkcwhivupa.cloudfront.net — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 108.156.248.214 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
Category: pua
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
21 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
Barely seen in the wild and first surfaced recently. 21 antivirus detections make that low prevalence materially relevant, but rarity alone is not proof of malware.
Fingerprint and provenance
- File name
- ncNeL7MAc.exe
- Format
- Win32 EXE
- Code signing
- Signature valid: Infivora
- Size
- 15.4 MB
- Last analyzed
- Sep 29, 2026, 11:02 AM UTC
c37ad5bdbb44f1af0b1fc7223c07fcee1a9d71d13a326bde5c006916771896fdSafety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
This file is dangerous. Treat it as harmful and remove it.
- Recovery step 01
Don't run this file. Delete this file from the device, then empty the Recycle Bin or Trash.
- Recovery step 02
If you already ran it, disconnect from the internet and start with a full antivirus scan or Microsoft Defender Offline scan. If compromise is suspected or the problem persists, use a reputable second-opinion scanner and follow incident-recovery or clean-reinstall guidance.
- Recovery step 03
If you typed any passwords while it was open, change them from a device you trust.
- Recovery step 04
Get a fresh copy from the developer's official site or an official app store.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is ncNeL7MAc.exe a virus?
What is ncNeL7MAc.exe?
How many antivirus engines detected ncNeL7MAc.exe?
What should I do if I already ran ncNeL7MAc.exe?
How do I remove ncNeL7MAc.exe?
What kind of malware is ncNeL7MAc.exe?
Is ncNeL7MAc.exe digitally signed?
What is the SHA-256 hash of ncNeL7MAc.exe?
How up to date is this analysis of ncNeL7MAc.exe?
Community
Member reviews and reports for this exact file hash.