MB-25620c7cd07faa860ae6777ca949a0e98108f36ff3ee3ae792959c9f4e124ead
high
📛 Threat Title
Unknown: armv5l
Description
File type: elf. Size: 7405752 bytes. Reporter: BlinkzSec. First seen: 2026-05-14 17:00:07.
Indicators of Compromise (3)
Each indicator is enriched from the IOC database, threat-intel feed corroboration (Threat Hunt) and VirusTotal. Click one to expand.
hash_sha256
25620c7cd07faa860ae6777ca949a0e98108f36ff3ee3ae792959c9f4e124ead
1 feed
IOC database
- Type
- hash_sha256
- Value
25620c7cd07faa860ae6777ca949a0e98108f36ff3ee3ae792959c9f4e124ead- First seen
- Last seen
- Attached to this threat
- Appears in
- 2 threats
- Description
- Unknown
Threat Hunt — feed corroboration
Listed by 1 threat-intel feed vendor: Abuse.ch. Open in Threat Hunt →
Details From VirusTotal
No VirusTotal details cached for this IOC. Open the IOC page to query VirusTotal.
hash_sha1
d004755daf6ee74fe7857fbcfa210c0b8ff3ecc0
VT: VT base fetch failed: HTTPError: 429 Client Error: Too Many Requests for url: https://www.virustotal.com/api/v3/files/d004755daf6ee74fe7857fbcfa210c0b8ff3ecc0
1 feed
IOC database
- Type
- hash_sha1
- Value
d004755daf6ee74fe7857fbcfa210c0b8ff3ecc0- First seen
- Last seen
- Attached to this threat
- Appears in
- 2 threats
Threat Hunt — feed corroboration
Listed by 1 threat-intel feed vendor: Abuse.ch. Open in Threat Hunt →
Details From VirusTotal
VirusTotal: VT base fetch failed: HTTPError: 429 Client Error: Too Many Requests for url: https://www.virustotal.com/api/v3/files/d004755daf6ee74fe7857fbcfa210c0b8ff3ecc0
hash_md5
48b11e0f53596ee42b5631cc78242450
VT: VT base fetch failed: HTTPError: 429 Client Error: Too Many Requests for url: https://www.virustotal.com/api/v3/files/48b11e0f53596ee42b5631cc78242450
2 feeds
IOC database
- Type
- hash_md5
- Value
48b11e0f53596ee42b5631cc78242450- First seen
- Last seen
- Attached to this threat
- Appears in
- 2 threats
Threat Hunt — feed corroboration
Listed by 2 threat-intel feed vendors: Abuse.ch, threatview.io. Open in Threat Hunt →
Details From VirusTotal
VirusTotal: VT base fetch failed: HTTPError: 429 Client Error: Too Many Requests for url: https://www.virustotal.com/api/v3/files/48b11e0f53596ee42b5631cc78242450
References (1)
-
MalwareBazaar sample page
Abuse.ch
File type: elf. Size: 7405752 bytes. Reporter: BlinkzSec. First seen: 2026-05-14 17:00:07.
Remediations (9)
-
web:github.com
The Intune Remediations collection is a set of script packages designed to detect and fix common support issues on user endpoints. Each script package includes a detection script, a remediation script, and metadata. By deploying these packages through Intune, you can proactively address issues before end-users even notice them, potentially reducing support calls.
-
web:learn.microsoft.com
Learn more about Remediations in Microsoft Intune, including what Remediations are and view any prerequisites and licensing requirements. Also, learn how to deploy built-in and custom remediation scripts, and learn how to monitor your scripts.
-
web:microsoft.github.io
This capability supports the "Assume Breach" principle of Zero Trust by ensuring continuous detection and mitigation of weaknesses. Reference Remediate machine vulnerability findings - Microsoft Defender for Cloud Vulnerability scanning in Defender for Servers Remediate vulnerabilities with Microsoft Defender Vulnerability Management
-
web:panorays.com
Discover the difference between remediation and mitigation in risk management and how each strategy impacts security and resilience.
-
web:techcommunity.microsoft.com
Device Remediation status misleading Maybe I'm just missing something here, but when a Remediation script repeats on a schedule, how can we tell if devices were remediated? All devices report "Without Issues" and ZERO devices fixed, but I know the script ran and fixed the problem weeks ago. Say I have 100 devices assigned to the script:
-
web:www.bugcrowd.com
Mitigation solutions include isolating a set of vulnerable resources from the rest of the network with segmentation, temporarily disabling an application, or blocking a port that could provide access to a vulnerable resource. Your choice usually isn't a straightforward either/or decision between vulnerability remediation and mitigation .
-
web:www.reddit.com
If you don't have the in house staff to perform the threat analysis or threat hunting, you need a SOC. You could look at black point cyber since your are a PAX 8 customer. You currently have the detection portion of EDR, but not the analysis and remediation piece. You can't compare Symantec to Sentinel One, they aren't the same. Sentinel One IMO, is a far superior product, and in the years we ...
-
web:www.secure.com
Learn the difference between vulnerability remediation and mitigation , and how a risk-based strategy can strengthen your security posture.
-
web:www.tenable.com
Learn what mean time to remediate (MTTR) means, why it matters and how to reduce MTTR in vulnerability and exposure management with Tenable solutions.
AI Forensic Analysis
Only Available for Registered Users. Sign in to view.