Bank Mellat Company Cyber Security Posture
bankmellat.irBank Mellat was established on 1979/12/20 by virtue of the resolution dated 1979/9/29 adopted by the General Assembly of Banks and pursuant to the provision of article 17 of the Bill on administering the Banks, with a paid up capital of Rls 33.5 bn as a merger of ten pre-revolution private banks comprising: Tehran, Dariush, Pars, Etebarat Taavoni& Tozie, Iran& Arab, Bein-al-melalie-Iran, Omran, Bimeh Iran, Tejarat Khareji Iran and Farhangian. Currently, the bank's capital amounts to Rls 40000 bn and is one of the largest commercial banks in the Islamic Republic of Iran, ranking among the top 1000 banks of the world.
Bank Mellat Company Details
bank-mellat
10,001+ employees
0
522
Banking
bankmellat.ir
Scan still pending
BAN_3045436
In-progress
Bank Mellat Risk Score (AI oriented)Between 800 and 900
This score is AI-generated and less favored by cyber insurers, who prefer the TPRM score.
Bank Mellat Global Score.png)
Bank Mellat Company Scoring based on AI Models
| Model Name | Date | Description | Current Score Difference | Score |
|---|---|---|---|---|
| AVERAGE-Industry | 03-12-2025 | This score represents the average cybersecurity rating of companies already scanned within the same industry. It provides a benchmark to compare an individual company's security posture against its industry peers. | N/A | Between 800 and 900 |
Bank Mellat Company Cyber Security News & History
| Entity | Type | Severity | Impact | Seen | Url ID | Details | View |
|---|
Bank Mellat Company Subsidiaries
Bank Mellat was established on 1979/12/20 by virtue of the resolution dated 1979/9/29 adopted by the General Assembly of Banks and pursuant to the provision of article 17 of the Bill on administering the Banks, with a paid up capital of Rls 33.5 bn as a merger of ten pre-revolution private banks comprising: Tehran, Dariush, Pars, Etebarat Taavoni& Tozie, Iran& Arab, Bein-al-melalie-Iran, Omran, Bimeh Iran, Tejarat Khareji Iran and Farhangian. Currently, the bank's capital amounts to Rls 40000 bn and is one of the largest commercial banks in the Islamic Republic of Iran, ranking among the top 1000 banks of the world.
Access Data Using Our API
Get company history
Rapid.png)
Bank Mellat Cyber Security News
The methods and menace of the new bank robbers
Attempts to rob banks online generally start with โphishingโ, or tricking an employee into downloading a benign-looking software, known as a โTrojanโ.
Deluge of Nearly 300 Fake Apps Floods Iranian Banking Sector
No Iranian bank customers are safe from financially motivated cybercriminals wielding convincing but fake mobile apps.
Charming Kitten Targets Iranian Dissidents with Advanced Cyber Attacks
Germany's BfV warns of ongoing cyber attacks by Charming Kitten, targeting Iranians in Germany.
Iran Says It Was Hit With โVery Bigโ Cyberattack (Published 2019)
Iranian media said the attack was the largest banking security breach in Iran's history. While there is constant cyberconflict between theย ...
Iranโs banks were hacked, minister admits, but experts doubt his claimed culprit
Hackers believed to be working for the Iranian government have targeted US government agencies, as well as sectors of the economy, including oilย ...
Iranian bank cyber attack leaves 15 million customers' details online
Iranian bank cyber attack leaves 15 million customers' details online ยท โThis is the largest financial scam in Iran's history,โ Iran's Aftab Newsย ...
15 Million Debit Cards Exposed as Iranian Banks Fall Victim to Cyber Warfare
The details of 15 million debit cards in Iran have been exposed online in the largest financial security breach in the history of the country.
Iran News in Brief โ December 9, 2023
THIS PAGE WILL BE UPDATED WITH THE LATEST NEWS UPDATE: 11:30 PM CET Nasdaq To Pay $4 Mln Settlement Over Apparent Iran Sanctions Violationsย ...
Iran Banks Burned, Then Customer Accounts Were Exposed Online (Published 2019)
The details of millions of Iranian bank cards were published online after antigovernment protests last month. Experts suspect a state-sponsored cyberattack.
Bank Mellat Similar Companies
Banco Sabadell
Banco Sabadell es el cuarto grupo bancario privado espaรฑol, integrado por diferentes bancos, marcas, sociedades filiales y sociedades participadas que abarcan todos los รกmbitos del negocio financiero bajo un denominador comรบn: profesionalidad y calidad. Un equipo humano joven y bien preparado, do
Punjab & Sind Bank
Punjab and Sind Bank was established in the year 1908, under the far-sighted vision of luminaries like Bhai Vir Singh, Sir Sunder Singh Majitha and Sardar Tarlochan Singh. It is a government-owned bank, headquartered at New Delhi, India. The principle mission of its foundation involves economic ai
Sumitomo Mitsui Trust Bank
Sumitomo Mitsui Trust Bank, Limited (SuMi TRUST) was established through the merger of The Sumitomo Trust and Banking Co., Ltd. with Chuo Mitsui Trust and Banking, Ltd. and Chuo Mitsui Asset Trust and Banking Company, Ltd. on April 1, 2012. SuMi TRUST is Japan's largest trust bank, with AUM of more
BNP Paribas Fortis
At BNP Paribas Fortis, we strive to be a trusted financial companion for all our customers. No matter how big or small their dreams and challenges, we are there to help. As the go-to source for all things banking, our customers can count on us for reliable guidance. We are ready to help them make
VakฤฑfBank
1954 yฤฑlฤฑnda, vakฤฑf kaynaklarฤฑnฤฑ ekonomik kalkฤฑnmanฤฑn gereksinimleri doฤrultusunda en iyi biรงimde deฤerlendirmek amacฤฑyla kurulan VakฤฑfBank, o gรผnden bu yana รงaฤdaล bankacฤฑlฤฑk yรถntemleri ve uygulamalarฤฑyla Tรผrkiyeโnin tasarruf dรผzeyinin geliลim sรผrecine katkฤฑda bulunmaktadฤฑr. VakฤฑfBank; bรถlgesinin e
The People's Bank of China
The People's Bank of China (PBC) was established on December 1, 1948 based on the consolidation of the Huabei Bank, the Beihai Bank and the Xibei Farmer Bank. In September 1983, the State Council decided to have the PBC function as a central bank. The Law of the People's Republic of China on the Peo
Frequently Asked Questions (FAQ) on Cybersecurity Incidents
Bank Mellat CyberSecurity History Information
Total Incidents: According to Rankiteo, Bank Mellat has faced 0 incidents in the past.
Incident Types: As of the current reporting period, Bank Mellat has not encountered any cybersecurity incidents.
Total Financial Loss: The total financial loss from these incidents is estimated to be {total_financial_loss}.
Cybersecurity Posture: The company's overall cybersecurity posture is described as Bank Mellat was established on 1979/12/20 by virtue of the resolution dated 1979/9/29 adopted by the General Assembly of Banks and pursuant to the provision of article 17 of the Bill on administering the Banks, with a paid up capital of Rls 33.5 bn as a merger of ten pre-revolution private banks comprising: Tehran, Dariush, Pars, Etebarat Taavoni& Tozie, Iran& Arab, Bein-al-melalie-Iran, Omran, Bimeh Iran, Tejarat Khareji Iran and Farhangian. Currently, the bank's capital amounts to Rls 40000 bn and is one of the largest commercial banks in the Islamic Republic of Iran, ranking among the top 1000 banks of the world..
Detection and Response: The company detects and responds to cybersecurity incidents through {description_of_detection_and_response_process}.
Incident Details
Incident 1: Ransomware Attack
Title: {Incident_Title}
Description: {Brief_description_of_the_incident}
Date Detected: {Detection_Date}
Date Publicly Disclosed: {Disclosure_Date}
Date Resolved: {Resolution_Date}
Type: {Type_of_Attack}
Attack Vector: {Attack_Vector}
Vulnerability Exploited: {Vulnerability}
Threat Actor: {Threat_Actor}
Motivation: {Motivation}
Incident 2: Data Breach
Title: {Incident_Title}
Description: {Brief_description_of_the_incident}
Date Detected: {Detection_Date}
Date Publicly Disclosed: {Disclosure_Date}
Date Resolved: {Resolution_Date}
Type: {Type_of_Attack}
Attack Vector: {Attack_Vector}
Vulnerability Exploited: {Vulnerability}
Threat Actor: {Threat_Actor}
Motivation: {Motivation}
Common Attack Types: As of now, the company has not encountered any reported incidents involving common cyberattacks.
Identification of Attack Vectors: The company identifies the attack vectors used in incidents through {description_of_identification_process}.
Impact of the Incidents
Incident 1: Ransomware Attack
Financial Loss: {Financial_Loss}
Data Compromised: {Data_Compromised}
Systems Affected: {Systems_Affected}
Downtime: {Downtime}
Operational Impact: {Operational_Impact}
Conversion Rate Impact: {Conversion_Rate_Impact}
Revenue Loss: {Revenue_Loss}
Customer Complaints: {Customer_Complaints}
Brand Reputation Impact: {Brand_Reputation_Impact}
Legal Liabilities: {Legal_Liabilities}
Identity Theft Risk: {Identity_Theft_Risk}
Payment Information Risk: {Payment_Information_Risk}
Incident 2: Data Breach
Financial Loss: {Financial_Loss}
Data Compromised: {Data_Compromised}
Systems Affected: {Systems_Affected}
Downtime: {Downtime}
Operational Impact: {Operational_Impact}
Conversion Rate Impact: {Conversion_Rate_Impact}
Revenue Loss: {Revenue_Loss}
Customer Complaints: {Customer_Complaints}
Brand Reputation Impact: {Brand_Reputation_Impact}
Legal Liabilities: {Legal_Liabilities}
Identity Theft Risk: {Identity_Theft_Risk}
Payment Information Risk: {Payment_Information_Risk}
Average Financial Loss: The average financial loss per incident is {average_financial_loss}.
Commonly Compromised Data Types: The types of data most commonly compromised in incidents are {list_of_commonly_compromised_data_types}.
Incident 1: Ransomware Attack
Entity Name: {Entity_Name}
Entity Type: {Entity_Type}
Industry: {Industry}
Location: {Location}
Size: {Size}
Customers Affected: {Customers_Affected}
Incident 2: Data Breach
Entity Name: {Entity_Name}
Entity Type: {Entity_Type}
Industry: {Industry}
Location: {Location}
Size: {Size}
Customers Affected: {Customers_Affected}
Response to the Incidents
Incident 1: Ransomware Attack
Incident Response Plan Activated: {Yes/No}
Third Party Assistance: {Yes/No}
Law Enforcement Notified: {Yes/No}
Containment Measures: {Containment_Measures}
Remediation Measures: {Remediation_Measures}
Recovery Measures: {Recovery_Measures}
Communication Strategy: {Communication_Strategy}
Adaptive Behavioral WAF: {Adaptive_Behavioral_WAF}
On-Demand Scrubbing Services: {On_Demand_Scrubbing_Services}
Network Segmentation: {Network_Segmentation}
Enhanced Monitoring: {Enhanced_Monitoring}
Incident 2: Data Breach
Incident Response Plan Activated: {Yes/No}
Third Party Assistance: {Yes/No}
Law Enforcement Notified: {Yes/No}
Containment Measures: {Containment_Measures}
Remediation Measures: {Remediation_Measures}
Recovery Measures: {Recovery_Measures}
Communication Strategy: {Communication_Strategy}
Adaptive Behavioral WAF: {Adaptive_Behavioral_WAF}
On-Demand Scrubbing Services: {On_Demand_Scrubbing_Services}
Network Segmentation: {Network_Segmentation}
Enhanced Monitoring: {Enhanced_Monitoring}
Incident Response Plan: The company's incident response plan is described as {description_of_incident_response_plan}.
Third-Party Assistance: The company involves third-party assistance in incident response through {description_of_third_party_involvement}.
Data Breach Information
Incident 2: Data Breach
Type of Data Compromised: {Type_of_Data}
Number of Records Exposed: {Number_of_Records}
Sensitivity of Data: {Sensitivity_of_Data}
Data Exfiltration: {Yes/No}
Data Encryption: {Yes/No}
File Types Exposed: {File_Types}
Personally Identifiable Information: {Yes/No}
Prevention of Data Exfiltration: The company takes the following measures to prevent data exfiltration: {description_of_prevention_measures}.
Handling of PII Incidents: The company handles incidents involving personally identifiable information (PII) through {description_of_handling_process}.
Ransomware Information
Incident 1: Ransomware Attack
Ransom Demanded: {Ransom_Amount}
Ransom Paid: {Ransom_Paid}
Ransomware Strain: {Ransomware_Strain}
Data Encryption: {Yes/No}
Data Exfiltration: {Yes/No}
Ransom Payment Policy: The company's policy on paying ransoms in ransomware incidents is described as {description_of_ransom_payment_policy}.
Data Recovery from Ransomware: The company recovers data encrypted by ransomware through {description_of_data_recovery_process}.
Regulatory Compliance
Incident 1: Ransomware Attack
Regulations Violated: {Regulations_Violated}
Fines Imposed: {Fines_Imposed}
Legal Actions: {Legal_Actions}
Regulatory Notifications: {Regulatory_Notifications}
Incident 2: Data Breach
Regulations Violated: {Regulations_Violated}
Fines Imposed: {Fines_Imposed}
Legal Actions: {Legal_Actions}
Regulatory Notifications: {Regulatory_Notifications}
Regulatory Frameworks: The company complies with the following regulatory frameworks regarding cybersecurity: {list_of_regulatory_frameworks}.
Ensuring Regulatory Compliance: The company ensures compliance with regulatory requirements through {description_of_compliance_measures}.
Lessons Learned and Recommendations
Incident 1: Ransomware Attack
Lessons Learned: {Lessons_Learned}
Incident 2: Data Breach
Lessons Learned: {Lessons_Learned}
Incident 1: Ransomware Attack
Recommendations: {Recommendations}
Incident 2: Data Breach
Recommendations: {Recommendations}
Key Lessons Learned: The key lessons learned from past incidents are {list_of_key_lessons_learned}.
Implemented Recommendations: The company has implemented the following recommendations to improve cybersecurity: {list_of_implemented_recommendations}.
References
Additional Resources: Stakeholders can find additional resources on cybersecurity best practices at {list_of_additional_resources}.
Investigation Status
Incident 1: Ransomware Attack
Investigation Status: {Investigation_Status}
Incident 2: Data Breach
Investigation Status: {Investigation_Status}
Communication of Investigation Status: The company communicates the status of incident investigations to stakeholders through {description_of_communication_process}.
Stakeholder and Customer Advisories
Incident 1: Ransomware Attack
Stakeholder Advisories: {Stakeholder_Advisories}
Customer Advisories: {Customer_Advisories}
Incident 2: Data Breach
Stakeholder Advisories: {Stakeholder_Advisories}
Customer Advisories: {Customer_Advisories}
Advisories Provided: The company provides the following advisories to stakeholders and customers following an incident: {description_of_advisories_provided}.
Initial Access Broker
Incident 1: Ransomware Attack
Entry Point: {Entry_Point}
Reconnaissance Period: {Reconnaissance_Period}
Backdoors Established: {Backdoors_Established}
High Value Targets: {High_Value_Targets}
Data Sold on Dark Web: {Yes/No}
Incident 2: Data Breach
Entry Point: {Entry_Point}
Reconnaissance Period: {Reconnaissance_Period}
Backdoors Established: {Backdoors_Established}
High Value Targets: {High_Value_Targets}
Data Sold on Dark Web: {Yes/No}
Monitoring and Mitigation of Initial Access Brokers: The company monitors and mitigates the activities of initial access brokers through {description_of_monitoring_and_mitigation_measures}.
Post-Incident Analysis
Incident 1: Ransomware Attack
Root Causes: {Root_Causes}
Corrective Actions: {Corrective_Actions}
Incident 2: Data Breach
Root Causes: {Root_Causes}
Corrective Actions: {Corrective_Actions}
Post-Incident Analysis Process: The company's process for conducting post-incident analysis is described as {description_of_post_incident_analysis_process}.
Corrective Actions Taken: The company has taken the following corrective actions based on post-incident analysis: {list_of_corrective_actions_taken}.
Additional Questions
General Information
Ransom Payment History: The company has {paid/not_paid} ransoms in the past.
Last Ransom Demanded: The amount of the last ransom demanded was {last_ransom_amount}.
Last Attacking Group: The attacking group in the last incident was {last_attacking_group}.
Incident Details
Most Recent Incident Detected: The most recent incident detected was on {most_recent_incident_detected_date}.
Most Recent Incident Publicly Disclosed: The most recent incident publicly disclosed was on {most_recent_incident_publicly_disclosed_date}.
Most Recent Incident Resolved: The most recent incident resolved was on {most_recent_incident_resolved_date}.
Impact of the Incidents
Highest Financial Loss: The highest financial loss from an incident was {highest_financial_loss}.
Most Significant Data Compromised: The most significant data compromised in an incident was {most_significant_data_compromised}.
Most Significant System Affected: The most significant system affected in an incident was {most_significant_system_affected}.
Response to the Incidents
Third-Party Assistance in Most Recent Incident: The third-party assistance involved in the most recent incident was {third_party_assistance_in_most_recent_incident}.
Containment Measures in Most Recent Incident: The containment measures taken in the most recent incident were {containment_measures_in_most_recent_incident}.
Data Breach Information
Most Sensitive Data Compromised: The most sensitive data compromised in a breach was {most_sensitive_data_compromised}.
Number of Records Exposed: The number of records exposed in the most significant breach was {number_of_records_exposed}.
Ransomware Information
Highest Ransom Demanded: The highest ransom demanded in a ransomware incident was {highest_ransom_demanded}.
Highest Ransom Paid: The highest ransom paid in a ransomware incident was {highest_ransom_paid}.
Regulatory Compliance
Highest Fine Imposed: The highest fine imposed for a regulatory violation was {highest_fine_imposed}.
Most Significant Legal Action: The most significant legal action taken for a regulatory violation was {most_significant_legal_action}.
Lessons Learned and Recommendations
Most Significant Lesson Learned: The most significant lesson learned from past incidents was {most_significant_lesson_learned}.
Most Significant Recommendation Implemented: The most significant recommendation implemented to improve cybersecurity was {most_significant_recommendation_implemented}.
References
Most Recent Source: The most recent source of information about an incident is {most_recent_source}.
Most Recent URL for Additional Resources: The most recent URL for additional resources on cybersecurity best practices is {most_recent_url}.
Investigation Status
Current Status of Most Recent Investigation: The current status of the most recent investigation is {current_status_of_most_recent_investigation}.
Stakeholder and Customer Advisories
Most Recent Stakeholder Advisory: The most recent stakeholder advisory issued was {most_recent_stakeholder_advisory}.
Most Recent Customer Advisory: The most recent customer advisory issued was {most_recent_customer_advisory}.
Initial Access Broker
Most Recent Entry Point: The most recent entry point used by an initial access broker was {most_recent_entry_point}.
Most Recent Reconnaissance Period: The most recent reconnaissance period for an incident was {most_recent_reconnaissance_period}.
Post-Incident Analysis
Most Significant Root Cause: The most significant root cause identified in post-incident analysis was {most_significant_root_cause}.
Most Significant Corrective Action: The most significant corrective action taken based on post-incident analysis was {most_significant_corrective_action}.
What Do We Measure?
Every week, Rankiteo analyzes billions of signals to give organizations a sharper, faster view of emerging risks. With deeper, more actionable intelligence at their fingertips, security teams can outpace threat actors, respond instantly to Zero-Day attacks, and dramatically shrink their risk exposure window.
These are some of the factors we use to calculate the overall score:
Identify exposed access points, detect misconfigured SSL certificates, and uncover vulnerabilities across the network infrastructure.
Gain visibility into the software components used within an organization to detect vulnerabilities, manage risk, and ensure supply chain security.
Monitor and manage all IT assets and their configurations to ensure accurate, real-time visibility across the company's technology environment.
Leverage real-time insights on active threats, malware campaigns, and emerging vulnerabilities to proactively defend against evolving cyberattacks.
