Back to all incidents

Hossner-Textil GmbH

hossner-textile.de
EMERGING

Hossner-Textil GmbH was listed on the Qilin ransomware extortion leak portal. Unverified extortion claim alleging unauthorized network access and data compromise.

Observable Status EMERGING
Industry / Sector Manufacturing
Incident Classification Network Intrusion & Data Exfiltration
Attributed Threat Actor Qilin
Affected Population Scope Under Audit
First Seen 2026-10-25
Last Updated 2026-10-25
Authentication Credentials
OPEN WEIGHTS TELEMETRY • DETERMINISTIC CONFIDENCE

Confidence & Source Corroboration

13% CONFIDENCE
1. Primary Authority UNVERIFIED CLAIM Base weight: 6%
2. Evidence Specificity +7% Domain & Scope Telemetry
3. Corroboration Curve +0% 1 independent domain
4. Timeline & Staleness +0% 1 milestone logged
Corroborated Source Domains:
ransomware.live

Technical Forensic Briefing

Incident Overview

Hossner-Textil GmbH, operating within the Manufacturing sector, has been subject to a cybersecurity incident. Ground-truth telemetry indicates the threat activity is attributed to threat actor Qilin.

Hossner-Textil GmbH was listed on the Qilin ransomware extortion leak portal. Unverified extortion claim alleging unauthorized network access and data compromise.

Compromised Assets & Data Scope

The specific volume of affected customer or organizational records remains under active forensic investigation. Primary affected online infrastructure and perimeter domains include hossner-textile.de.

Specific classes of compromised records, credentials, or proprietary information continue to be audited through ongoing forensic investigation.

Authoritative Directives & Vendor Disclosures

  • Continuous Telemetry Monitoring: Formal statutory regulatory filings (SEC Form 8-K, State AG portals) and sovereign agency advisories (CISA, NCSC) are continuously monitored via automated ingestion pipeline.

Milestone Timeline (1 events logged)

2026-10-25 17:17 UTC
UNVERIFIED CLAIM

Hossner-Textil GmbH Listed on Qilin Ransomware Extortion Portal

Have updated information or a new verifiable source?

This incident record is a flat Markdown file tracked in Git. Propose an update or add a milestone via Pull Request.

Propose Update via GitHub