RegistroCiberVE
All incidents
unconfirmed ransomware claim Public report: Date confidence: Low

Presunto compromiso de EPK atribuido a NightSpire

EPK (epkweb.com) apareció como presunto objetivo de NightSpire en un registro de monitoreo descubierto el 19 de mayo de 2025, que estima el ataque para el 18 sin publicar su fundamento. Hackmanac lo incluye en la semana del 14 al 20 de mayo. Otra ficha de BreachSense, descubierta el 20, atribuye27 GB al reclamo; una tarjeta preservada por FalconFeeds separa ese volumen alegado de los 50 GB atribuidos a BranchCore. Las fuentes documentan un listado y cifras reclamadas, no el archivo o su autenticidad. No se verificaron la fecha original del actor, intrusión, ejecución de ransomware, cifrado, exfiltración, interrupción, recuperación o pérdidas.

Overview

Missing evidence

confirmación o respuesta de EPKpublicación primaria verificable de NightSpireevidencia independiente de intrusión, ransomware ejecutado, cifrado o exfiltraciónmuestra o conjunto de datos recuperable y volumen validadovector de accesointerrupción, recuperación y pérdidas materiales

Impact details

Las fuentes documentan un reclamo de NightSpire contra EPK y una cifra alegada de27 GB en un rastreador y una tarjeta separada de BranchCore. No se autenticaron el archivo, su origen, volumen, acceso, cifrado, exfiltración, publicación efectiva o efectos operativos. El estado del servicio permanece desconocido.

Classification & severity

Category
Undetermined
Subtype
unconfirmed ransomware claim
Confidence
Low

Dos rastreadores preservan el emparejamiento NightSpire/EPK, pero ninguno muestra la publicación primaria o prueba que ransomware fuera ejecutado, que existiera cifrado o que datos fueran extraídos.

Severity assessment

Sólo se preservó un reclamo target-specific. Sin artefacto primario, confirmación de EPK, datos verificables, interrupción o impacto, la severidad no puede determinarse.

Timeline

Discovery

Ransomware.live registró públicamente a EPK/epkweb.com como objetivo reclamado por NightSpire; no preserva la publicación primaria.

Evidence & sources

4 sources

Hackmanac incluyó a NightSpire y EPK en una lista de ataques reclamados o divulgados

Hackmanac Team May 20, 2025
Corroborating Security research Source confidence: Medium

What this source supports

  • weekly table titled LIST OF ATTACKS (CLAIMED OR DISCLOSED) contains a NightSpire / EPK row
  • the row gives ESIX 4.25 but no incident date, domain, country text, volume, actor artifact or technical evidence
  • the same table separately lists Branchcore Technology

Evidence limits

Secondary weekly tracker. Its claimed-or-disclosed label does not distinguish an actor claim from victim disclosure, and no evidence supports the underlying event.

Relevance to this case

Independent publisher corroboration that the NightSpire/EPK pairing circulated publicly, not independent technical confirmation.

Ransomware.live registró a EPK como objetivo reclamado por NightSpire

Ransomware.live / Julien Mousqueton May 19, 2025
Primary Security research Source confidence: Medium

What this source supports

  • Ransomware.live identifies EPK, epkweb.com and Nightspire and says the group claimed the target
  • record was discovered 19 May 2025 and gives an estimated attack date of 18 May
  • page provides no actor post, description, file, sample, volume or technical validation

Evidence limits

Target-specific tracker record, not a victim statement or technical investigation. The current Hudson Rock credential panel is separate enrichment and is not evidence for the historical claim.

Relevance to this case

Most specific attached source for target/domain/group and tracker dates; it establishes a claim record only.

EPK tracker listing: NightSpire and claimed 27 GB

BreachSense
Context Security research Source confidence: Low

What this source supports

  • The public tracker lists epkweb.com under NightSpire.
  • Tracker discovery is May 20,2025.
  • The entry states a claimed leak size of27GB, without authenticated content or a validation method.

Evidence limits

Specific listing and alleged-size provenance only. It does not validate intrusion, encryption, acquisition, exfiltration, underlying actor-post time or full-corpus size. The separate credential-enrichment panel explicitly disclaims necessary linkage and is not used as incident evidence.

Relevance to this case

Restores omitted provenance for the27 GB allegation while retaining unconfirmed event status.

FalconFeeds claim listing: EPK 27 GB separately from BranchCore 50 GB

FalconFeeds.io (@FalconFeedsio) May 19, 2025
Primary Social media Source confidence: Medium

What this source supports

  • The current preserved source review reports a separate EPK card with a27GB allegation, distinct from BranchCore 50 GB.

Evidence limits

EPK 27 GB allegation is preserved in the current BranchCore source graph. Fresh X request yielded an empty body; this is historical claim provenance, not newly authenticated post/media, full dataset, intrusion, encryption or independent validation. Do not transfer BranchCore dates or quantity to EPK.

Relevance to this case

Supplies cross-record provenance for an EPK-specific listing detail, not incident confirmation.