Hibiscus Petroleum Berhad Company Cyber Security Posture
hibiscuspetroleum.comHibiscus Petroleum Berhad (Hibiscus Petroleum) is Malaysia’s first listed independent oil and gas exploration and production company. Our key activities are focused on monetising producing oilfields and growing our portfolio of development and producing assets in areas of our geographical focus: the United Kingdom, Malaysia and Australia. As an operator of offshore oil and gas producing fields, our efforts are focused on enhancing operational efficiencies to safely deliver high-margin production from our assets. Our growth strategy in the current oil and gas market is to leverage on opportunities that are present within our portfolio of existing assets and make quality acquisitions on a selective basis, thus delivering sustainable returns to our shareholders. We are committed towards upholding high standards of safety and environmental management. We also prioritise corporate governance, whilst expanding our business on strong technical and commercial foundations. Hibiscus Petroleum is headquartered in Kuala Lumpur, and our securities are listed on the Main Market of Bursa Malaysia Securities Berhad. Hibiscus Petroleum is a constituent on the FTSE4Good Bursa Malaysia Index as well as the FTSE4Good Bursa Malaysia Shariah Index. Hibiscus Petroleum securities have been classified as being Shariah-compliant by the Shariah Advisory Council of the Securities Commission of Malaysia.
HPB Company Details
hibiscus-petroleum-berhad
577 employees
51916
211
Oil and Gas
hibiscuspetroleum.com
Scan still pending
HIB_3722888
In-progress
HPB Risk Score (AI oriented)Between 800 and 900
This score is AI-generated and less favored by cyber insurers, who prefer the TPRM score.
HPB Global Score.png)
Hibiscus Petroleum Berhad 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 |
Hibiscus Petroleum Berhad Company Cyber Security News & History
| Entity | Type | Severity | Impact | Seen | Url ID | Details | View |
|---|---|---|---|---|---|---|---|
| Hibiscus Petroleum Berhad | Cyber Attack | 60 | 2 | 10/2019 | HIB82915423 | Link | |
Rankiteo Explanation : Attack limited on finance or reputationDescription: Hibiscus Petroleum said that its IT system was subjected to an attack and the affected parts of the system were isolated and partially shut down by the firm. Hibiscus said the system was gradually being restored and that production operations had not been impacted. | |||||||
Hibiscus Petroleum Berhad Company Subsidiaries
Hibiscus Petroleum Berhad (Hibiscus Petroleum) is Malaysia’s first listed independent oil and gas exploration and production company. Our key activities are focused on monetising producing oilfields and growing our portfolio of development and producing assets in areas of our geographical focus: the United Kingdom, Malaysia and Australia. As an operator of offshore oil and gas producing fields, our efforts are focused on enhancing operational efficiencies to safely deliver high-margin production from our assets. Our growth strategy in the current oil and gas market is to leverage on opportunities that are present within our portfolio of existing assets and make quality acquisitions on a selective basis, thus delivering sustainable returns to our shareholders. We are committed towards upholding high standards of safety and environmental management. We also prioritise corporate governance, whilst expanding our business on strong technical and commercial foundations. Hibiscus Petroleum is headquartered in Kuala Lumpur, and our securities are listed on the Main Market of Bursa Malaysia Securities Berhad. Hibiscus Petroleum is a constituent on the FTSE4Good Bursa Malaysia Index as well as the FTSE4Good Bursa Malaysia Shariah Index. Hibiscus Petroleum securities have been classified as being Shariah-compliant by the Shariah Advisory Council of the Securities Commission of Malaysia.
Access Data Using Our API
Get company history
Rapid.png)
HPB Cyber Security News
Zones Eyes $3B Revenue Milestone As Demand For AI, Cybersecurity Soars
Zones CEO Firoz Lalji said he plans to focus on cybersecurity, AI enablement and service delivery.
Vermont’s Dual-Enrollment Cybersecurity Certificate
A Vermont partnership gives high school students hands-on experience in cybersecurity and a conditional acceptance to a local college.
New executive order targets federal cybersecurity gaps
The latest cybersecurity order sets some new standards and direction, but it also goes back and makes changes to Biden-era executive orders. If ...
Cybersecurity essentials for the future: From hype to what works
Discover actionable cybersecurity essentials to boost visibility, reduce risk, strengthen controls, align security with business outcomes.
French cybersecurity agency confirms government affected by Ivanti hacks
ANSSI, France's cyber agency, says a hacking campaign targeted “organizations from governmental, telecommunications, media, finance, ...
Cybersecurity unicorn Cato Networks snags $359m, soaring to $4.8 billion valuation
Cato Networks, a maker of cloud-based, secured networks for large enterprises that lets remote workers connect to applications regardless of ...
Cybersecurity M&A Roundup: 41 Deals Announced in June 2025
Forty-one cybersecurity merger and acquisition (M&A) deals were announced in June 2025 and added to SecurityWeek tracker.
You won’t believe how this teen became Microsoft’s youngest cybersecurity star
Dylan isn't your average school student. He started working with Microsoft at 13 and has already filed dozens of security bugs.
Cyberattack hits major airline, up to 6M customer profiles exposed
Qantas warns millions about a cyberattack compromising personal data including names and emails, following FBI alerts about the "Scattered ...
HPB Similar Companies
Equinor
We're Equinor, an international energy company with a proud history. Formerly Statoil, we are 20,000 committed colleagues developing oil, gas, wind and solar energy in more than 30 countries worldwide. We’re the largest operator in Norway, among the world’s largest offshore operators, and a growing
Amec Foster Wheeler
Wood Group has combined with Amec Foster Wheeler to form a new global leader in the delivery of project, engineering and technical services to energy and industrial markets. To find out more about Wood visit our new website at www.woodplc.com For all the latest updates and job news follow Wood on L
PT OMS Oilfield Services
OMS Oilfield Services is one of the largest single operators of machine shops providing Oil Country Tubular Goods (OCTG) repair, manufacturing and recertification services in Asia and the Middle East. We operate ten full fledged facilities in seven countries, with a well established reputation for h
McDermott International, Ltd
McDermott is a premier provider of engineering and construction solutions to the energy industry. Our customers trust our technology-driven approach—engineered to responsibly harness and transform global energy resources into the products the world needs for now and what’s next. From concept to co
Ecopetrol
Ecopetrol (NYSE: EC) es la compañía más grande en Colombia y uno de los principales grupos de energía de Latinoamérica. Cuenta con más de 18.000 empleados y es responsable del 60% de la producción de hidrocarburos en Colombia. Es propietaria de las dos refinerías del Colombia y de la gran pa
Reliance Industries Limited
Our motto “Growth is Life” aptly captures the ever-evolving spirit of Reliance. Our activities span hydrocarbon exploration and production, petroleum refining and marketing, petrochemicals, retail, and telecommunications. In each of these areas, we are committed to innovation-led, exponential growth
Frequently Asked Questions (FAQ) on Cybersecurity Incidents
HPB CyberSecurity History Information
Total Incidents: According to Rankiteo, HPB has faced 1 incidents in the past.
Incident Types: The types of cybersecurity incidents that have occurred include ['Cyber Attack'].
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 Hibiscus Petroleum Berhad (Hibiscus Petroleum) is Malaysia’s first listed independent oil and gas exploration and production company. Our key activities are focused on monetising producing oilfields and growing our portfolio of development and producing assets in areas of our geographical focus: the United Kingdom, Malaysia and Australia. As an operator of offshore oil and gas producing fields, our efforts are focused on enhancing operational efficiencies to safely deliver high-margin production from our assets. Our growth strategy in the current oil and gas market is to leverage on opportunities that are present within our portfolio of existing assets and make quality acquisitions on a selective basis, thus delivering sustainable returns to our shareholders. We are committed towards upholding high standards of safety and environmental management. We also prioritise corporate governance, whilst expanding our business on strong technical and commercial foundations. Hibiscus Petroleum is headquartered in Kuala Lumpur, and our securities are listed on the Main Market of Bursa Malaysia Securities Berhad. Hibiscus Petroleum is a constituent on the FTSE4Good Bursa Malaysia Index as well as the FTSE4Good Bursa Malaysia Shariah Index. Hibiscus Petroleum securities have been classified as being Shariah-compliant by the Shariah Advisory Council of the Securities Commission of Malaysia..
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.
