We have completed our review of the security incident at our infrastructure vendor, Northflank, and are marking this incident resolved.
Northflank hosted background job workers for Quiltt only; no customer-facing traffic was routed through it. The environment variables exposed there included credentials for our production database and Redis. We rotated every credential held in that environment, including those two, immediately after Northflank's notification, and redeployed the affected services.
What we found
Northflank's forensics place the first known decryption of affected secrets between 02:39 and 03:08 UTC on 30 October.
Our review of production database, network, application, and job queue logs across the exposure window and through the credential rotation found no unauthorized access, no anomalous queries, and no evidence that customer or end-user data was accessed or copied.
Customer-facing services were not interrupted during the incident or the response.
Northflank's investigation and an independent forensic review remain ongoing. If any finding changes our assessment, we will post an update here and contact affected customers directly.
No components marked as affected
Resolved
We have completed our review of the security incident at our infrastructure vendor, Northflank, and are marking this incident resolved.
Northflank hosted background job workers for Quiltt only; no customer-facing traffic was routed through it. The environment variables exposed there included credentials for our production database and Redis. We rotated every credential held in that environment, including those two, immediately after Northflank's notification, and redeployed the affected services.
What we found
Northflank's forensics place the first known decryption of affected secrets between 02:39 and 03:08 UTC on 30 October.
Our review of production database, network, application, and job queue logs across the exposure window and through the credential rotation found no unauthorized access, no anomalous queries, and no evidence that customer or end-user data was accessed or copied.
Customer-facing services were not interrupted during the incident or the response.
Northflank's investigation and an independent forensic review remain ongoing. If any finding changes our assessment, we will post an update here and contact affected customers directly.
Monitoring
We are monitoring a security incident disclosed today by Northflank, one of our infrastructure vendors. Northflank has advised customers to assume their environment variables were compromised.
No customer traffic is served from Northflank — all customer-facing web traffic runs on our primary hosting providers. Background workers did run there with production database and Redis credentials. We have rotated every credential exposed to that environment.
Our review of production database, network, application, and job queue logs found no evidence of unauthorized access to customer data.
Customer-facing services have not been interrupted. We will post further updates here if anything changes.
Monitoring
We are monitoring a security incident disclosed today by Northflank, one of our infrastructure vendors. Northflank has advised all customers to assume their environment variables were compromised.
No customer traffic was served from Northflank — all customer-facing web traffic runs on our primary hosting providers. Background workers did run there with production database and Redis credentials. As a precaution we rotated every credential exposed to that environment, including those production database and Redis credentials, and we are reviewing access logs for any unauthorized use.
Customer-facing services were not interrupted. We will update this incident as Northflank's investigation develops and our log review completes.