1-minute read
What a defender needs to know
Check Point Research read ten exposed ARTEX operator databases. One operator directed agents at ten gray-market iOS signing shops; over roughly two weeks the agents obtained more than 300 certificates and passwords. Three passed checks for a matching key, valid certificate and in-house provisioning profile. The person mostly asked about progress while agents looked for hardcoded admin credentials, unauthenticated APIs, weak passwords and web-execution flaws.
A separate crypto operator’s agents produced 230 findings across 292 objectives, but the attacker’s wallet had no recorded transactions. An agent did gain AWS S3 write access through credentials leaked by an unauthenticated API and changed a crypto service’s landing-page manifest; the owner later restored it. Check Point says the write succeeded but the compromise was not properly exercised.
If you run an app-signing service, remove admin secrets from delivered JavaScript and HTML, require authorization on certificate-store APIs, and limit signing-library reads to the service identities that need them. Correlate short bursts of varied web requests with certificate-store access and credential reads. Revoke or rotate exposed keys and replace affected profiles; test externally for 401 or 403 with no .p12 key bytes on an unauthorized API read, and verify retired keys fail signing. If you run ARTEX yourself, restrict its panel and database to an access-controlled management path and test their reachability from outside.
