Navitas Petroleum
bd_f253dc6bf99c6681 · schema v1 · pii pii-v1
Full breach record for Navitas Petroleum →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Black Basta on its public extortion blog. It has not been validated by the victim or any regulator. Treat attribution and counts as the threat actor's assertion until a regulatory filing or victim disclosure corroborates them.
Source: Ransomware.live
Post text · scraped from the leak site
Navitas Petroleum is a publicly traded (TASE:NVPT.L) North America focused, O&G exploration and production partnership. Navitas Petroleum has an established asset portfolio, including: conventional onshore production (Neches field), robust offshore production (Buckskin project), development stage assets (post-FID Shenandoah project) and high-impact exploration prospects (Block 7, offshore Canada).SITE: www.navitaspet.com Address 5847 San Felipe #2200 Houston, Texas 77057 UNITED STATES [REDACTED-PHONE] Ext 402FULL DATA SIZE: 330gb 1. Accounting 2. HR 3. W-9 forms 4. ConfidentialityNETWORK: PELES-------------------------DOMAIN ADMINS------------------------- AdministratorPELES\Administrator Pr0t3ctM3!!!-------------------------DC------------------------- DC01-Peles.Peles.local 10.10.1.30 Windows Server 2019 Standard-------------------------SERVERS------------------------- License01-Peles.Peles.local Windows Server 2019 Standard ACCT01-PELES.Peles.local 10.10.1.39 Windows Server 2019 Standard FS01-Peles.Peles.local 10.10.1.34 Windows Server 2019 Standard Citrix01-Peles.Peles.local 10.10.1.32 Windows Server 2019 Standard Citrix02-Peles.Peles.local 10.10.1.33 Windows Server 2019 Standard VDA01-Peles.Peles.local 10.10.1.29 Windows Server 2019 Standard Petra01-Peles.Peles.local 10.10.1.38 Windows Server 2016 Standard scada01-Peles.Peles.local Windows Server 2016 Standard
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Dec 18, 2023
Claim posted
—
No filing yet · watching
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Claim → filing
—
Compliance clock
Not assessable
Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.
No regulatory filing corroborates this yet — it is the attacker's own assertion. Watch this entity to be notified the moment a filing corroborates or contradicts it.
Source ceiling
- actor name
- victim claim
- ransom/leak status
- discovery date
- materiality
- notification
- affected count
- confirmed data types
- compliance clock
The ✕ fields stay blank until a regulatory filing or victim disclosure lands.