Is MagicActions_Latest.crx safe?
No antivirus engine detected the Chrome extension, and one sandbox found no offensive behavior, though its direct-IP contacts lack a completed reputation check.
All 76 antivirus engines were free of detections, including 17 tier-1 engines, and the completed sandbox run produced no malware verdict or offensive techniques. Direct-IP traffic was observed, but its reputation was not fully checked; this limits certainty without outweighing the otherwise consistent evidence.
df9a8a4ea4f83d656f…5c013a02034f22Recommended next actions
Before opening
Open it only when its sender or download source is one you independently trust.
If you already opened 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.
All 76 antivirus engines were free of detections, including 17 tier-1 engines, and the completed sandbox run produced no malware verdict or offensive techniques. Direct-IP traffic was observed, but its reputation was not fully checked; this limits certainty without outweighing the otherwise consistent evidence.
The Chrome extension received no malicious or suspicious detections from 76 engines, with all 17 reporting tier-1 engines remaining silent. One completed sandbox run observed browser-extension techniques T1176 and T1185 but no offensive techniques, persistence indicators, or malware verdict. Ten extracted files were inspected without a malicious-child finding, although their individual verdicts remain unknown. A medium-severity direct-IP heuristic fired after seven external unicast contacts, and no complete host-reputation cross-check is available. No YARAify, CIRCL, or MalwareBazaar intelligence corroborated malware activity.
What We Detected
No malicious or suspicious detection appeared among 76 antivirus engines. Seventeen tier-1 engines, including Avast, BitDefender, ESET-NOD32, Kaspersky, and Microsoft, reported no detection. Research intelligence also returned no YARAify rules, CIRCL match, or MalwareBazaar record.
Threat Behavior
One sandbox run loaded and unpacked the Chrome extension. It recorded T1176 and T1185, which are compatible with extension and browser activity, but found no offensive techniques, persistence indicators, or malicious sandbox verdict. A direct-IP heuristic fired because seven external unicast IP addresses were contacted without recorded application domains. Because contactedHosts is unavailable, those contacts do not have a complete reputation result. Ten extracted files were inspected without a malicious-child finding, but their individual classifications remain unknown.
What To Do Now
Install the extension only from its official browser-store listing or verified publisher channel, and review the permissions Chrome requests. Keep browser and endpoint protection enabled, especially if the package came from an unofficial download site.
Where this verdict could be wrong2 caveats
- MalwareTips.Synth.DirectIpC2 fired because the sandbox recorded seven external unicast IP addresses without application domains; no complete host-reputation result is available because contactedHosts=null.
- The 10 extracted child files have unknown individual verdicts despite droppedChildren.hasMaliciousChild=false, limiting assurance about their contents.
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/76 engines reported malicious or suspicious detections.
- engines.tier1Malicious=0 and engines.tier1ReportedClean=17.
- behaviour.offensiveCount=0 and behaviour.hasMaliciousSandboxVerdict=false.
- droppedChildren.hasMaliciousChild=false after 10 inspected children.
- externalIntel.yaraify.ruleCount=0, externalIntel.circl.hit=false, and externalIntel.malwareBazaar.hit=false.
- MalwareTips.Synth.DirectIpC2 fired for seven external unicast IP contacts.
- contactedHosts=null, so no complete reputation cross-check exists for observed IP contacts.
- All 10 extracted child files retain unknown individual verdicts.
- file.reputation=0 and prevalence.timesSubmitted=12 provide limited reputation history.
Use the extension only when obtained from its official listing and its requested permissions match the advertised features. Keep Chrome and endpoint protection enabled.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 76 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial8 runtime contacts were observed without a completed reputation cross-check.
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
- 2MITRE ATT&CK techniques
- 6spawned processes
- 8network contacts
- 18filesystem & mutex artifacts
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
MagicActions_Latest.crx
df9a8a4ea4f83d656fd94898011ebb3e75f8be400a439fcbb75c013a02034f22
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Program Files\Google\Chrome\Application\chrome.exe" --load-extension=C:\Users\<USER>\AppData\Local\Temp\sample "http://about:blank"
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Program Files\Google\Chrome\Application\chrome.exe" --type=crashpad-handler "--user-data-dir=C:\Users\<USER>\AppData\Local\Google\Chrome\User Data" /prefetch:4 --monitor-self-annotation=ptype=crashpad-handler "--database=C:\Users\<USER>\AppData\Local\Google\Chrome\User Data\Crashpad" --url=https://clients2.google.com/cr/report --annotation=channel= --annotation=plat=Win64 --annotation=prod=Chrome --annotation=ver=141.0.7390.108 --initial-client-data=0x200,0x204,0x208,0x1bc,0x20c,0x7ffa3f8d0868,0x7ffa3f8d0874,0x7ffa3f8d0880
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
_locales
C:\chrome\_locales
04Isolated runtime analysis - Written fileObserved
en
C:\chrome\_locales\en
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
173.194.202.84
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
192.178.163.94
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.
- 173.194.202.84
- 192.178.163.94
- 173.194.203.141
- 192.178.163.190
- 74.125.135.113
- 173.194.203.188
- 142.250.99.100
- 224.0.0.251
- C:\chrome\_locales
- C:\chrome\_locales\en
- C:\chrome\_locales\en\messages.json
- C:\chrome\_metadata
- C:\chrome\_metadata\verified_contents.json
- C:\Users\user\AppData\Local\Google\Chrome\User Data\Default\e483cfd1-5fe0-4d18-99df-c44b5abdf0fa.tmp
- C:\chrome\_metadata
- C:\chrome\_metadata\verified_contents.json
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 28e391060106b4036d6c…e356c6Never scannednever seen before
- 2e27ac7706dc08d93c11…57ff93Never scannednever seen before
- eea40256b526e353abb2…0777c5Never scannednever seen before
- 4d9ccef0b8161497cade…57dbb6Never scannednever seen before
- 58970dd60fbc73c8a9c4…ce9e9dNever scannednever seen before
- 28c3140facb17ed97644…aa99c7Never scannednever seen before
- b14f358cfdada01e1dcd…1bd3a4Never scannednever seen before
- 897eff05c412fe8cb9c7…7264d4Never scannednever seen before
- c8d3bf1db39f734c3da4…19bd67Never scannednever seen before
- ed8fd76fe892d5aa4ee7…07a4edNever 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
- 0 / 76engines flagged
- 10sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
0 of 76 antivirus engines flagged the file.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has been submitted 12 times from 10 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 03
Scanned file: MagicActions_Latest.crx — df9a8a4ea4f83d656fd94898011ebb3e75f8be400a439fcbb75c013a02034f22
ProvenanceObservedSourceUploaded fileObserved at - 04
Observed process — "C:\Program Files\Google\Chrome\Application\chrome.exe" --load-extension=C:\Users\<USER>\AppData\Local\Temp\sample "http://about:blank"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 05
Observed process — "C:\Program Files\Google\Chrome\Application\chrome.exe" --type=crashpad-handler "--user-data-dir=C:\Users\<USER>\AppData\Local\Google\Chrome\User Data" /prefetch:4 --monitor-self-annotation=ptype=crashpad-handler "--database=C:\Users\<USER>\AppData\Local\Google\Chrome\User Data\Crashpad" --url=https://clients2.google.com/cr/report --annotation=channel= --annotation=plat=Win64 --annotation=prod=Chrome --annotation=ver=141.0.7390.108 --initial-client-data=0x200,0x204,0x208,0x1bc,0x20c,0x7ffa3f8d0868,0x7ffa3f8d0874,0x7ffa3f8d0880
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
File written: _locales — C:\chrome\_locales
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: en — C:\chrome\_locales\en
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
Contacted host: 173.194.202.84 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 192.178.163.94 — 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.
The 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.
Evidence173.194.202.84 · 192.178.163.94 · 173.194.203.141
0 of 76 engines flagged this file
View all 76 engine results
PE structure
Not applicablePE structure analysis applies to Windows executable formats, not this file type.
How widely this file has been seen
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- MagicActions_Latest.crx
- Format
- Google Chrome Extension
- Code signing
- Not applicable to this file type
- Size
- 169.6 KB
- Last analyzed
- Sep 9, 2026, 6:27 PM UTC
df9a8a4ea4f83d656fd94898011ebb3e75f8be400a439fcbb75c013a02034f22Safety & 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
Open it only when its sender or download source is one 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 MagicActions_Latest.crx safe?
What is MagicActions_Latest.crx?
How many antivirus engines detected MagicActions_Latest.crx?
What is the SHA-256 hash of MagicActions_Latest.crx?
Is it safe to open MagicActions_Latest.crx?
How up to date is this analysis of MagicActions_Latest.crx?
Community
Member reviews and reports for this exact file hash.