Unknown
Zero detections on a brand-new unsigned file with minimal submission history.
eab72b33b408dfbfac…44331c4345The reasoning behind this verdict
The MT AI Engine weighs every signal from this scan — antivirus detections, sandbox behaviour, code signing, prevalence and historical matches — to reach a single, evidence-based verdict.
All 61 reporting engines returned clean results with no tier-1 or low-trust malicious detections. The file is unsigned and has no prior similar-hash matches. Its rare_new prevalence classification and three-day age indicate insufficient exposure for reliable assessment. External intelligence sources also returned no hits. Low coverage combined with the complete absence of malicious signals leads to an unknown verdict.
Each signal cites a concrete token from the evidence the arbiter saw — engine name, MITRE technique, signer string, or an exact count.
engines.malicious=0 and engines.tier1Malicious=0 across 61 reporting engines
prevalence.classification=rare_new with uniqueSources=1
signing.signed=false and signerStats.found=false
externalIntel.yaraify.ruleCount=0 and externalIntel.circl.knownMalicious=null
- zero malicious detections across 61 engines
- no external intelligence hits
- rare_new prevalence with only one submission
- unsigned file with no signer history
Treat the file as unverified until additional analysis data becomes available.
What to do now
There isn't enough information to give this file a clear rating.
Be cautious — an unknown rating is not the same as a clean bill of health.
Only run it if it came directly from the official maker of the software.
When in doubt, don't open it — or scan it again later once it's more widely seen.
0 detections across 74 engines
How widely this file has been seen
Barely seen in the wild and first surfaced recently. This is the footprint of targeted malware the AV industry hasn't signatured yet — extra scrutiny is warranted.
Forensic fingerprint
- File name
- 抽象鸣潮 菲比.ysm
- Size
- 238.9 KB
- MIME type
- application/octet-stream
- Detected type
- unknown
- SHA-256
- eab72b33b408dfbfacbc0cf03c487b873f6884a582c1fe09969fda44331c4345
- MD5
- a44682dee4ebe60881e1d1ff2628c503
- SHA-1
- 82b67ee423aa3ce89abcad3b9ca343d4fd18409e
- First seen (VT)
- 7/5/2026, 11:39:40 AM
- Last analysis (VT)
- 7/5/2026, 11:39:40 AM
- First scan (MalwareTips)
- 7/5/2026, 11:40:23 AM
- Last scan (MalwareTips)
- 7/8/2026, 1:25:50 AM
Safety FAQ
Common questions about 抽象鸣潮 菲比.ysm, answered from the scan data above.
- We can't give 抽象鸣潮 菲比.ysm a confident verdict yet — too few engines have an opinion on this exact file. Uncommon or brand-new files often show little coverage before vendors catch up, so treat it as untrusted: don't opened it unless you're certain of the source.
- 抽象鸣潮 菲比.ysm is a file (application/octet-stream), about 239 KB. We identify a file by its cryptographic hash rather than its name, because the same filename can be reused by completely different files — the hash below is the reliable fingerprint.
- None — all 74 antivirus engines we queried report 抽象鸣潮 菲比.ysm as clean. That's reassuring, though brand-new malware can briefly evade detection before vendors add signatures, so we also weigh the file's behaviour and reputation.
- The SHA-256 hash of 抽象鸣潮 菲比.ysm is eab72b33b408dfbfacbc0cf03c487b873f6884a582c1fe09969fda44331c4345, and its MD5 is a44682dee4ebe60881e1d1ff2628c503. This hash is the file's unique fingerprint — two files with the same SHA-256 are identical. Use it to confirm you're looking at exactly this file (not just one with the same name) when comparing against antivirus databases or a download's published checksum.
- This report reflects the scan run on July 5, 2026. Because a file's hash never changes, the identity of 抽象鸣潮 菲比.ysm is fixed — but antivirus coverage improves over time, so a file that looks clean today can pick up detections later (and vice-versa). If you need the latest picture, MalwareTips staff can re-run the analysis from scratch.
Reviews & malware reports(0)
Tell the community what you saw. Tag the sample — Trojan, Adware, False Positive — and share what the file did on your system. Your report helps confirm or dispute the AV verdict.