Evergrowing Bank Company Cyber Security Posture

egbank.com.cn

Evergrowing Banking was established on 2003 after joint-stock system reform, now it has grown to a famous national joint-stock bank. The heaquarter of the bank is in city of Yantai, Shandong Province, with 11 tier-one branches in Qingdao, Jinan, Hangzhou, Chengdu, Chongqing, Yantai, Fuzhou, Kunming, Xi'an, Ningbo, Suzhou; and 15 tier-two branches in Suzhou, Shaoxing, Dongying, Yiwu, Jining, Binzhou, Leshan, Wenzhou, Wuxi, Dazhou, nanchong, Liaocheng, Dezhou, Weifang, Nantong; with overall 148 networks. At curently, Evergrowing Bank prepares to open Beijing and Shanghai Branches. In 2008, Evergrowing Bank succesffully introduced UOB as Strategy Investor.ฤƒย€ย€ฤƒย€ย€ Evergrowing bank earned the prize of China Top 500 Companies, China Trustworthy Company, Top 10 Trustworthy Company of China Economy, 30 Years Creative Brand of China, etc. Evergrowing Bank is Tier One Dealer in China Open Market of Central Bank. Treausry Bond Underwriter of Ministry of Finance, The National Inter Bank Bond Market Bilateral Market Maker, National Policy Financial Bonds Primary Underwriter, The National Bonds Underwriter, The Enterprise Short-term Financing Bond Underwriter, The NationaI Inter Bank Bond Market Clearing Agents, Member of The natinoal Debt Association , Member and Shareholder of Unionpay, and many other license of market entrance.

Evergrowing Bank Company Details

Linkedin ID:

evergrowing-bank

Employees number:

10,001+ employees

Number of followers:

0

NAICS:

522

Industry Type:

Banking

Homepage:

egbank.com.cn

IP Addresses:

Scan still pending

Company ID:

EVE_4403756

Scan Status:

In-progress

AI scoreEvergrowing Bank Risk Score (AI oriented)

Between 800 and 900

This score is AI-generated and less favored by cyber insurers, who prefer the TPRM score.

globalscoreEvergrowing Bank Global Score
blurone
Ailogo

Evergrowing Bank Company Scoring based on AI Models

Model NameDateDescriptionCurrent Score DifferenceScore
AVERAGE-Industry03-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

Evergrowing Bank Company Cyber Security News & History

Past Incidents
0
Attack Types
0
EntityTypeSeverityImpactSeenUrl IDDetailsView

Evergrowing Bank Company Subsidiaries

SubsidiaryImage

Evergrowing Banking was established on 2003 after joint-stock system reform, now it has grown to a famous national joint-stock bank. The heaquarter of the bank is in city of Yantai, Shandong Province, with 11 tier-one branches in Qingdao, Jinan, Hangzhou, Chengdu, Chongqing, Yantai, Fuzhou, Kunming, Xi'an, Ningbo, Suzhou; and 15 tier-two branches in Suzhou, Shaoxing, Dongying, Yiwu, Jining, Binzhou, Leshan, Wenzhou, Wuxi, Dazhou, nanchong, Liaocheng, Dezhou, Weifang, Nantong; with overall 148 networks. At curently, Evergrowing Bank prepares to open Beijing and Shanghai Branches. In 2008, Evergrowing Bank succesffully introduced UOB as Strategy Investor.ฤƒย€ย€ฤƒย€ย€ Evergrowing bank earned the prize of China Top 500 Companies, China Trustworthy Company, Top 10 Trustworthy Company of China Economy, 30 Years Creative Brand of China, etc. Evergrowing Bank is Tier One Dealer in China Open Market of Central Bank. Treausry Bond Underwriter of Ministry of Finance, The National Inter Bank Bond Market Bilateral Market Maker, National Policy Financial Bonds Primary Underwriter, The National Bonds Underwriter, The Enterprise Short-term Financing Bond Underwriter, The NationaI Inter Bank Bond Market Clearing Agents, Member of The natinoal Debt Association , Member and Shareholder of Unionpay, and many other license of market entrance.

Loading...

Access Data Using Our API

SubsidiaryImage

Get company history

curl -i -X GET 'https://api.rankiteo.com/underwriter-getcompany-history?linkedin_id=evergrowing-bank' -H 'apikey: YOUR_API_KEY_HERE'
newsone

Evergrowing Bank Cyber Security News

2025-05-29T12:00:00.000Z
Navy Federal's credit play, Coinbase outage and more banking tech news

Going into June, bankers are honed in on Navy Federal Credit Union's partnership with Bloom Credit, a data breach at Coinbase and other techย ...

2024-09-13T07:00:00.000Z
Cybersecurity in Banking: Threats, Solutions & Best Practices

Encryption, firewalls, and secure access controls are just a few of the measures that banks implement to ensure customer data remains protected.

2025-01-14T08:00:00.000Z
The โ€˜Largest Illicit Online Marketplaceโ€™ Ever Is Growing at an Alarming Rate, Report Says

The 'Largest Illicit Online Marketplace' Ever Is Growing at an Alarming Rate, Report Says. Huione Guarantee, a gray market researchers believeย ...

2025-01-14T08:00:00.000Z
Huione: the company behind the largest ever illicit online marketplace has launched a stablecoin

Huione Guarantee is a Telegram-based marketplace serving fraudsters in South East Asia, including those responsible for so-called โ€œpigย ...

2024-11-11T08:00:00.000Z
What is Lockbit? The digital extortion gang on a cybercrime spree

A cyber-criminal group named Lockbit, which on Friday said it breached the Industrial and Commercial Bank of China (ICBC), has hacked some of the world'sย ...

2024-03-11T07:00:00.000Z
The cyber clock is ticking: Derisking emerging technologies in financial services

As financial institutions actively adopt emerging technologies, they should act now to future-proof themselves against growing cyber risks.

2018-09-14T07:00:00.000Z
How a Cyber Attack Could Cause the Next Financial Crisis

An attack on a computer processing or communications network could cause $50 billion to $120 billion of economic damage, a loss rankingย ...

2023-10-01T07:00:00.000Z
Bank BTN focuses Capex on IT security

BTN implements 3 (three) layers of cyber security: IT security, IT management risk, and compliance and IT audit. These 3 layers will giveย ...

2023-11-15T08:00:00.000Z
Fiserv attack exposes 837K Flagstar Bank clients

Flagstar Bank's vendor, Fiserv was breached over MOVEit Transfer attacks, exposing the bank's customers.

similarCompanies

Evergrowing Bank Similar Companies

NatWest Business

At NatWest weโ€šร„รดre committed to helping British businesses grow. We give you access to the latest insights & analysis from industry experts and our partners. If you need to ask a question about your account with us, the quickest way to get in touch is via webchat. Visit our Business homepage: htt

National Bank of Egypt (NBE)

Since its inception in 1898 with a capital of GBP1 million, NBE has been regarded as one of the oldest and most respected commercial banks in Egypt.Never isolated from national issues or concerns, NBE has been the primary supporter of Egyptโ€™s national economy by financing the major Egyptian national

HDFC Bank is one of India's premier banks providing a wide range of financial products and services to over 43 million customers. Promoted by Housing Development Finance Corporation (HDFC), India's leading housing finance company, HDFC Bank began operations in 1995 with a simple mission: to be a "W

Banca Transilvania

Bun gasit. Noi suntem banca oamenilor intreprinzatori. ๐Ÿ’› Sau mai bine spus, compania care isi doreste ca lucrurile sa fie facute, ideile valorificate, iar visele implinite, sustinand oamenii care au curajul sa faca lucrurile putin mai diferit. Multi cred ca bankingul e doar despre bani, credite si

At BBVA we are leading the transformation of banking worldwide, united in pursuing our goal of bringing the age of opportunity to everyone. Firmly focused on the future, our on-going digital transformation is already producing disruptive innovations that power our vision of banking. Every one of o

CaixaBank

We are the leading financial group in the Spanish market, comprised of banking business, insurance activity and investments in international banks and leading companies in the services sector. CaixaBank is a financial group with a socially responsible, long-term universal banking model, based on qua

faq

Frequently Asked Questions (FAQ) on Cybersecurity Incidents

Evergrowing Bank CyberSecurity History Information

Total Incidents: According to Rankiteo, Evergrowing Bank has faced 0 incidents in the past.

Incident Types: As of the current reporting period, Evergrowing Bank 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 Evergrowing Banking was established on 2003 after joint-stock system reform, now it has grown to a famous national joint-stock bank. The heaquarter of the bank is in city of Yantai, Shandong Province, with 11 tier-one branches in Qingdao, Jinan, Hangzhou, Chengdu, Chongqing, Yantai, Fuzhou, Kunming, Xi'an, Ningbo, Suzhou; and 15 tier-two branches in Suzhou, Shaoxing, Dongying, Yiwu, Jining, Binzhou, Leshan, Wenzhou, Wuxi, Dazhou, nanchong, Liaocheng, Dezhou, Weifang, Nantong; with overall 148 networks. At curently, Evergrowing Bank prepares to open Beijing and Shanghai Branches. In 2008, Evergrowing Bank succesffully introduced UOB as Strategy Investor.ฤƒย€ย€ฤƒย€ย€ Evergrowing bank earned the prize of China Top 500 Companies, China Trustworthy Company, Top 10 Trustworthy Company of China Economy, 30 Years Creative Brand of China, etc. Evergrowing Bank is Tier One Dealer in China Open Market of Central Bank. Treausry Bond Underwriter of Ministry of Finance, The National Inter Bank Bond Market Bilateral Market Maker, National Policy Financial Bonds Primary Underwriter, The National Bonds Underwriter, The Enterprise Short-term Financing Bond Underwriter, The NationaI Inter Bank Bond Market Clearing Agents, Member of The natinoal Debt Association , Member and Shareholder of Unionpay, and many other license of market entrance..

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

Ransomware Logo

Incident 1: Ransomware Attack

Regulations Violated: {Regulations_Violated}

Fines Imposed: {Fines_Imposed}

Legal Actions: {Legal_Actions}

Regulatory Notifications: {Regulatory_Notifications}

Data Breach Logo

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

Incident 1: Ransomware Attack

Source: {Source}

URL: {URL}

Date Accessed: {Date_Accessed}

Incident 2: Data Breach

Source: {Source}

URL: {URL}

Date Accessed: {Date_Accessed}

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?

revertimgrevertimgrevertimgrevertimg
Incident
revertimgrevertimgrevertimgrevertimg
Finding
revertimgrevertimgrevertimgrevertimg
Grade
revertimgrevertimgrevertimgrevertimg
Digital Assets

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:

Network Security

Identify exposed access points, detect misconfigured SSL certificates, and uncover vulnerabilities across the network infrastructure.

SBOM (Software Bill of Materials)

Gain visibility into the software components used within an organization to detect vulnerabilities, manage risk, and ensure supply chain security.

CMDB (Configuration Management Database)

Monitor and manage all IT assets and their configurations to ensure accurate, real-time visibility across the company's technology environment.

Threat Intelligence

Leverage real-time insights on active threats, malware campaigns, and emerging vulnerabilities to proactively defend against evolving cyberattacks.

Top LeftTop RightBottom LeftBottom Right
Rankiteo is a unified scoring and risk platform that analyzes billions of signals weekly to help organizations gain faster, more actionable insights into emerging threats. Empowering teams to outpace adversaries and reduce exposure.
Users Love Us Badge