Is Automatic.dll safe?
Only Cylance issued a generic low-trust detection among 74 engines, while runtime, host-reputation, child-file, and external-intelligence checks supplied no corroborating malware evidence.
The lone alert is a generic Cylance detection, with no tier-1 engine support among 74 engines. One sandbox run produced no malicious verdict or offensive technique, and complete reputation checks of the 22 observed contacts found no known malicious or suspicious hosts; however, the file is unsigned.
1ceddaa3e0c2c5ec82…5a8f8657ebea0aRecommended next actions
Before using
Use it only as part of software obtained from the developer's official site or another source you independently trust.
If you already used it
Keep normal device protection enabled and stop if the file behaves unexpectedly.
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 lone alert is a generic Cylance detection, with no tier-1 engine support among 74 engines. One sandbox run produced no malicious verdict or offensive technique, and complete reputation checks of the 22 observed contacts found no known malicious or suspicious hosts; however, the file is unsigned.
Only 1 of 74 engines flagged the sample, and that alert came from Cylance with the generic label “Unsafe”; no tier-1 engine detected it. The completed sandbox run recorded no malicious verdict, no offensive technique, and no malicious dropped child. Reputation checks covered all 22 distinct observed contacts and found no known malicious or suspicious hosts. The LSASS heuristic is a counter-signal, but its listed evidence merely shows lsass.exe among running processes and does not demonstrate memory access. The unsigned status and two imphash-only suspicious precedents warrant ordinary caution, but they do not outweigh the broad absence of independent corroboration.
What We Detected
Cylance was the only engine to flag the file among 74 engines, using the generic label “Unsafe.” No tier-1 engine detected it, and 16 tier-1 engines reported no detection. Research intelligence produced no MalwareBazaar, CIRCL, or YARAify match.
Threat Behavior
One completed sandbox run returned no malicious verdict and recorded zero offensive techniques. A heuristic associated the presence of lsass.exe with credential-dumping activity, but the supplied evidence does not show memory access or credential extraction. Four dropped files were inspected without a malicious child, and reputation checks covered all 22 distinct observed contacts without finding a known malicious or suspicious host.
What To Do Now
The evidence most strongly supports an isolated false positive. Because the executable is unsigned, obtain it from the expected official source, verify its SHA-256 value, and keep endpoint protection enabled before use.
Where this verdict could be wrong3 caveats
- signing.applicable=true but the executable is unsigned, so no publisher identity or signer history supports it.
- triggeredHeuristics[0] reported a credential-dumper pattern involving lsass.exe, although the supplied evidence only shows that Windows process in the process list.
- similarHashes shows 2/3 prior verdicts as suspicious for matchKind=imphash, but signerMatchesSubject=false for every match and imphash-only similarity is weak.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- No tier-1 engine detected the sample among 74 engines.
- The completed sandbox run produced no malicious verdict and zero offensive techniques.
- All 22 distinct observed contacts received complete reputation coverage with no malicious or suspicious matches.
- No malicious dropped child or external-intelligence match was found.
- PE analysis found no packing or high-entropy code.
- The executable is unsigned and has no established publisher history.
- Cylance issued one generic low-trust “Unsafe” detection.
- A medium-severity heuristic inferred LSASS targeting, although the evidence does not demonstrate access.
- Two imphash-only similar samples previously received suspicious assessments.
Use only a copy obtained from the expected official source and verify SHA-256 1ceddaa3e0c2c5ec820bbd6cd6cf670e04547ffebca49aaa2e5a8f8657ebea0a. Keep antivirus and endpoint protection enabled.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete1 of 74 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial22 of 42 contacted hosts were cross-checked; coverage is incomplete.
YARA
Complete1 signature or behavior rule 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
- 8MITRE ATT&CK techniques
- 15spawned processes
- 42network contacts
- 25filesystem & mutex artifacts
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.
- aka.ms
- edge-mobile-static.azureedge.net
- business.bing.com
- js.monitor.azure.com
- microsoftmscompoc.tt.omtrdc.net
- img-prod-cms-rt-microsoft-com.akamaized.net
- w.usabilla.com
- d6tizftlrpuof.cloudfront.net
- westus2-0.in.applicationinsights.azure.com
- xpaywalletcdn.azureedge.net
- 96.7.170.175
- 13.107.246.38
- 13.107.6.158
- 23.205.110.18
- 52.70.251.18
- 3.161.239.93
- 20.9.155.145
- 3.161.239.204
- 20.125.209.212
- 150.171.27.10
- https://cmg3.cl/otros/banner_old.png?t=638880786699873046
- http://clients2.google.com/time/1/current?cup2key=8:irbtBughPoLLGhn5qKu_zJC1pC19dGq4hWVxxSl5OsY&cup2hreq=e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
- HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\SlowContextMenuEntries
- HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\5.0\Cache\Cookies\CachePrefix
- HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\5.0\Cache\History\CachePrefix
- HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\W32Time\Config\LastKnownGoodTime
- C:\Windows\ServiceProfiles\LocalService\AppData\Local\FontCache\Fonts\Download-1.tmp
- C:\Users\<USER>\AppData\Local\Temp\edge_BITS_6996_1425409113\BITF298.tmp
- C:\Users\<USER>\AppData\Local\Temp\edge_BITS_6996_1425409113\2ef98485-cbad-4d99-b4c2-cd4abac73fb4
- C:\Users\<USER>\AppData\Local\Temp\edge_BITS_6996_1224582416\BIT1360.tmp
- C:\Users\<USER>\AppData\Local\Temp\edge_BITS_6996_1224582416\64ecc27e-03e9-4f61-94ad-5eb160d62a35
- C:\Users\user\AppData\Local\Google\Chrome\User Data\BrowserMetrics\BrowserMetrics-68F4B42F-19D8.pma
- C:\Users\user\AppData\Local\Google\Chrome\User Data\Default\195c87de-6b8f-4eaf-984e-feaf7f0062b1.tmp
- C:\Users\user\AppData\Local\Google\Chrome\User Data\Default\Network\SCT Auditing Pending Reports~RF60d60.TMP
- C:\Users\user\AppData\Local\Google\Chrome\User Data\Default\Preferences~RF5f18b.TMP
- C:\Users\user\AppData\Local\Google\Chrome\User Data\Default\Secure Preferences~RF5f15c.TMP
- \Sessions\1\BaseNamedObjects\DBWinMutex
Files this sample writes at runtime
This file drops 4 children at runtime. None are currently flagged malicious in our cache.
- 249481479621334a8a6a…3bd6a6Never scannednever seen before
- 16a19763520bc5acfa82…a4042fNever scannednever seen before
- 0d20debb26fc8b2bc84f…798941Clean0/74 enginestrust 91from our cache
- e3b0c44298fc1c149afb…52b855Never 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.
- 1rule hit recorded
- 1 / 74engines flagged
- 32sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
1 of 74 antivirus engines flagged the file, including Cylance.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has been submitted 38 times from 32 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 03
Scanned file: Automatic.dll — 1ceddaa3e0c2c5ec820bbd6cd6cf670e04547ffebca49aaa2e5a8f8657ebea0a
ProvenanceObservedSourceUploaded fileObserved at - 04
Observed process — "C:\Users\<USER>\Desktop\program.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 05
Observed process — "C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe" --single-argument https://aka.ms/dotnet-core-applaunch?framework=Microsoft.NETCore.App&framework_version=6.0.0&arch=x64&rid=win-x64&os=win10&gui=true
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
File written: Download-1.tmp — C:\Windows\ServiceProfiles\LocalService\AppData\Local\FontCache\Fonts\Download-1.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: BITF298.tmp — C:\Users\<USER>\AppData\Local\Temp\edge_BITS_6996_1425409113\BITF298.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
Contacted host: aka.ms — Saved reputation verdict: safe.
ProvenanceDerivedSourceContacted-host cross-checkObserved at - 09
Contacted host: edge-mobile-static.azureedge.net — 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
Behavioral heuristics matched patterns associated with malware. Corroborating evidence determines how much weight they carry.
1 of 74 engines flagged this file
View all 74 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
- Automatic.dll
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 751.4 KB
- Last analyzed
- Sep 25, 2026, 7:59 AM UTC
1ceddaa3e0c2c5ec820bbd6cd6cf670e04547ffebca49aaa2e5a8f8657ebea0aSafety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
This file appears low risk based on the evidence available now.
- Recovery step 01
Use it only as part of software obtained from the developer's official site or another source you independently trust.
- Recovery step 02
A clean result reduces known risk, but it cannot guarantee that every new or targeted threat has been detected.
- Recovery step 03
Keep your antivirus and Windows updates switched on so you stay protected.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is Automatic.dll safe?
What is Automatic.dll?
How many antivirus engines detected Automatic.dll?
What is the SHA-256 hash of Automatic.dll?
Is it safe to use Automatic.dll?
How up to date is this analysis of Automatic.dll?
Community
Member reviews and reports for this exact file hash.