TF-MAL-osx.kitmos
📛 Threat Title
Malware family: Kitmos
Description
ThreatFox malware family `osx.kitmos`. Printable name: Kitmos. Aliases: KitM.
Indicators of Compromise (1)
Each indicator is enriched from the IOC database, threat-intel feed corroboration (Threat Hunt) and VirusTotal. Click one to expand.
domain
osx.kitmos
VT: VT base fetch failed: HTTPError: 429 Client Error: Too Many Requests for url: https://www.virustotal.com/api/v3/domains/osx.kitmos
IOC database
- Type
- domain
- Value
osx.kitmos- First seen
- Last seen
- Attached to this threat
- Appears in
- 1 threat
- Description
- Extracted from Threat TF-MAL-osx.kitmos
Threat Hunt — feed corroboration
Not present in any configured threat-intel feed.
Details From VirusTotal
VirusTotal: VT base fetch failed: HTTPError: 429 Client Error: Too Many Requests for url: https://www.virustotal.com/api/v3/domains/osx.kitmos
References (1)
- ThreatFox: IOCs for this family ThreatFox Malwares
Remediations (10)
-
web:arxiv.org
Interpretable models are especially important in ad-versarial domains such as malware analysis, where understanding the rationale behind a classification can guide remediation efforts and enhance model robust-ness. This paper proposes a novel approach for detect-ing and explaining concept drift in malware families over time.
-
web:atlas.utdallas.edu
This article outlines the responsibilities of users, including employees, students, and faculty, who create and maintain personal webpages to ensure that the content is appropriate, accurate, and accessible to all users.
-
web:cyberarrangedaily.substack.com
1. EtherRAT → Gentleman Ransomware: Malware Evolution & C2 Takedown Keywords:EtherRAT, TukTuk, Gentleman ransomware, CVE-2025-55182, C2 dismantlingSource: The DFIR Report The EtherRAT family—starting as a Linux-based RAT exploiting CVE-2025-55182 (React2Shell)—expanded to Windows and became part of the Gentleman ransomware operation.
-
web:malpedia.caad.fkie.fraunhofer.de
Details for the Kitmos malware family including references, samples and yara signatures.
-
web:spycloud.com
7 Incident Response Steps to Fully Remediate Malware Infections The following malware incident response steps are an addendum to your malware incident response plan to make for a more comprehensive approach to remediation , and can be incorporated into your existing IR runbooks.
-
web:www.bitdefender.com
According to the advisory (FLASH-20260219-001), cybercriminals are increasingly deploying sophisticated malware — particularly variants of the Ploutus family — to force Automated Teller Machines (ATMs) to dispense cash without any legitimate transaction or bank authorization.
-
web:www.breachsense.com
Complete malware remediation now requires addressing both the infected endpoint and the stolen authentication data. Your malware incident response playbook must account for both.
-
web:www.cisa.gov
It highlights technical approaches to uncovering malicious activity and includes mitigation steps according to best practices. The purpose of this report is to enhance incident response among partners and network administrators along with serving as a playbook for incident investigation.
-
web:www.mdpi.com
Artificial intelligence (AI) systems increasingly depend on complex, multi-stage supply chains that incorporate pre-trained models, third-party datasets, open-source libraries, and automated training pipelines. This dependency creates a rapidly expanding attack surface in which model poisoning, dependency compromise, and provenance manipulation can undermine system integrity long before ...
-
web:www.ncsc.gov.uk
How to defend organisations against malware or ransomware attacks.
AI Forensic Analysis
Only Available for Registered Users. Sign in to view.