The Sourcing Company

Summary

The Sourcing Company experienced a cyber incident affecting its online presence, as evidenced by an inaccessible blog page returning a "404 Not Found" error on its primary domain. This disruption indicated compromised web server functionality, though specific attack vectors or data impacts were not disclosed due to the lack of available incident details. The organization's public-facing services hosted on Apache servers became unreachable during the event, limiting visibility into operational consequences or remediation efforts. No further technical or forensic particulars were provided through the affected communication channel.

Motives

Detailed motive labels are available to members.

TTPs

Detailed technique labels are available to members.

Description

On March 27, 2022, The Sourcing Company (TSC) experienced a cyber incident that prompted the organization to publish an official blog post titled "Cyberincident Treft TSC" on its website. The post was hosted at the URL https://thesourcingcompany.nl/blogs/cyberincident-treft-tsc/ but returned a "404 Not Found" error when accessed. This error indicated the webpage was unavailable on TSC's Apache web server running on port 80. The absence of accessible content prevented public dissemination of incident details through this channel. No technical specifics regarding the nature of the compromise, initial attack vectors, or intrusion timeline were disclosed in the available source material. The HTTP status code suggested either deliberate removal of the announcement or unintended disruption of web services following the security event.

The unavailability of TSC's incident disclosure prevented confirmation of affected systems, operational impacts, data compromise scope, or containment measures undertaken by the organization. No supplemental information about threat actor attribution, malware involvement, forensic findings, or remediation efforts appeared in the accessible artifact. The 404 error persisted as the sole observable indicator of an operational disruption tied to the announced incident. TSC did not provide alternative communication channels or secondary publications containing incident details within the available evidentiary record. The organization's public-facing web infrastructure remained partially non-functional for at least this specific incident-related content at the time of reporting.

Sources

Sources available to members: 1 source.