Is Edgefield.py safe?
Python script with zero engine detections, clean sandbox verdict, and widespread benign history.
All 75 engines returned clean. One sandbox run showed no malicious verdict and the file has been submitted 39k times by 3.7k sources with no malicious children or host hits.
5a2d8e648e3f4cbdcd…8bb7088cefad79Recommended next actions
Before running
Run it only when it came from the developer's official site or another source you independently trust.
If you already ran 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 75 engines returned clean. One sandbox run showed no malicious verdict and the file has been submitted 39k times by 3.7k sources with no malicious children or host hits.
Zero malicious detections across 75 engines including 17 tier-1 engines rules out any named malware family. The single sandbox execution produced no malicious verdict and the two inspected contacted hosts carry no malicious reputation. Widespread prevalence (common_old) and absence of dropped malicious children further support a benign classification.
What We Detected
Python file Edgefield.py (8.9 KB) submitted 554 days ago. 0/75 engines flagged it malicious; 17 tier-1 engines explicitly returned clean. Sandbox executed once with no malicious verdict and no malicious dropped children.
Threat Behavior
One heuristic noted direct-IP traffic (T1571), but the two inspected hosts are not in our malicious cache. No persistence, registry changes, or C2 domains observed.
What To Do Now
File can be considered safe for normal use. Keep endpoint protection enabled.
Where this verdict could be wrong1 caveat
- communityComments contain two conflicting FileScan.IO verdicts (NO_THREAT vs MALICIOUS) — low weight given unanimous engine silence.
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 engines malicious
- common_old prevalence
- clean sandbox verdict
No action required; the file shows consistent clean signals across engines and sandbox analysis.
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 22 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
- 10MITRE ATT&CK techniques
- 15spawned processes
- 23network contacts
- 16filesystem & 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
Edgefield.py
5a2d8e648e3f4cbdcd32cbd2bb0ba48d10de32fe14042e201a8bb7088cefad79
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
xterm -hold -e /usr/bin/python /tmp/KanaSensei.py
02Isolated runtime analysis - ProcessObserved
Observed process
/usr/bin/python /tmp/KanaSensei.py
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
tty
/dev/tty
04Isolated runtime analysis - Written fileObserved
ptmx
/dev/ptmx
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
17.253.83.199
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
17.253.83.200
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.
- 17.253.83.199
- 17.253.83.200
- 17.253.5.208
- 17.253.5.207
- 17.253.82.113
- 17.253.82.241
- 64.78.200.1
- 17.248.195.71
- 17.253.82.245
- 64.78.201.1
- http://ocsp.comodoca.com/MFcwVaADAgEAME4wTDBKMAkGBSsOAwIaBQAEFOsl2JD%2BJyD0HX1qwV7vds9iz6t4BBR1cacZSBm8nZ3qQUfflMRId5nTeQIRAJjBcnaqg2kI3NxbTvi9QXQ%3D
- http://ocsp.comodoca.com/MFcwVaADAgEAME4wTDBKMAkGBSsOAwIaBQAEFOsl2JD+JyD0HX1qwV7vds9iz6t4BBR1cacZSBm8nZ3qQUfflMRId5nTeQIRAJjBcnaqg2kI3NxbTvi9QXQ=
- http://ocsp.usertrust.com/MFYwVKADAgEAME0wSzBJMAkGBSsOAwIaBQAEFM0w0kw0OoKrHwVwFYrXoQd2KZLpBBRTeb9aqitKz1SA4dibwJ3ysgNmywIQXfq7lXfPq2cfx93%2B0c8gWw%3D%3D
- /dev/tty
- /dev/ptmx
- /dev/pts/0
- /System/Volumes/Data/.fseventsd/000000000001b0bb
- /Users/user1/Library/Logs/Adobe/Acrobat Updater DC.log
- \Sessions\1\BaseNamedObjects\Local\SessionImmersiveColorMutex
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 14d02f4336c0717cc339…ca6438Never scannednever seen before
- 637f2274431905371a25…0b7b41Never scannednever seen before
- b0772744647d739f341d…0dd9dfNever scannednever seen before
- ec7b9444a9c5b3fe77b2…391e79Never scannednever seen before
- bc6022a315e015d61fb5…e00927Never scannednever seen before
- 40dd5f9bde58233b919a…48390bNever scannednever seen before
- 8d290961581a2efe57dc…e7f9b6Never scannednever seen before
- cc7bea957f25fbea54c0…f4a2f7Never scannednever seen before
- c1f0a7e187ffbdbfb81c…262657Never scannednever seen before
- 2053856f72913e34ce71…367006Never 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 / 75engines flagged
- 3,751sources 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 75 antivirus engines flagged the file.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has a long, established submission history across 3,751 sources.
Verdict inputView chapterProvenanceDerivedSourceSubmission historyObserved at - 03
The hash has been submitted 39,419 times from 3,751 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: Edgefield.py — 5a2d8e648e3f4cbdcd32cbd2bb0ba48d10de32fe14042e201a8bb7088cefad79
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — xterm -hold -e /usr/bin/python /tmp/KanaSensei.py
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — /usr/bin/python /tmp/KanaSensei.py
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: tty — /dev/tty
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: ptmx — /dev/ptmx
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 17.253.83.199 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 17.253.83.200 — 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.
Evidence17.253.83.199 · 17.253.83.200 · 17.253.5.208
0 of 75 engines flagged this file
View all 75 engine results
PE structure
Not applicablePE structure analysis applies to Windows executable formats, not this file type.
How widely this file has been seen
Widely seen in the wild for a long time. High prior this is legitimate; isolated detections on common-old files are usually false positives.
Fingerprint and provenance
- File name
- Edgefield.py
- Format
- Python
- Code signing
- Not applicable to this file type
- Size
- 8.7 KB
- Last analyzed
- Aug 4, 2026, 12:58 PM UTC
5a2d8e648e3f4cbdcd32cbd2bb0ba48d10de32fe14042e201a8bb7088cefad79Safety & 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
Run it only when it came 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 Edgefield.py safe?
What is Edgefield.py?
How many antivirus engines detected Edgefield.py?
What is the SHA-256 hash of Edgefield.py?
Is it safe to run Edgefield.py?
How up to date is this analysis of Edgefield.py?
Community
Member reviews and reports for this exact file hash.