iCreatAI News
Skip to content
Trending storyUpdating

Bitrise publishes ARTEX AI attack investigation report

1 reports1 sources17 hr agoUpdated

Understand this story

AI overview

Bitrise releases a security incident report, stating that between October 25 and November 18, 2026, someone manipulated the open-source AI penetration testing platform ARTEX to launch attacks against it. ARTEX first scanned more than 20 hostnames under the guise of "authorized penetration testing," and on November 13 logged in through an internal test bot account that had been unused since 2022 and did not have two-factor authentication enabled; about 11 minutes later it began using the workspace's cloud keys, ultimately reading signing files, build logs, and keys. Bitrise stated that files in 15 customer workspaces were accessed without authorization, including 1 code signing certificate file (the attacker was unable to obtain the password required to open the file), 1 description file, and 13 diagnostic build logs from May 2026. Bitrise said the platform is safe to use, but still recommends that customers rotate the keys, tokens, and certificates stored in Bitrise and reconnect GitHub.

AI overview based on source reports · Updated 2 hr ago

Coverage timeline

Follow the coverage to explore different perspectives.

Nov 20
  1. Hacker News AIFeatured
    Anatomy of an AI-driven attack: What ARTEX looks like in action

    Bitrise published an evidence-graded incident report describing how ARTEX, an open-source AI penetration-testing platform, probed its public surface from October 25, 2026, returned as an ordinary customer on November 12, and on November 13 signed in to a dormant internal test bot account without two-factor authentication, then chained stolen cloud keys over about ten hours. Bitrise detected the activity at 16:32 UTC, shut the platform down at 20:34 UTC, revoked all 919 cloud service-account keys, rotated every production secret and credential it manages, and rebuilt its build infrastructure; when the attacker returned on November 18, every attempt was refused. Files in 15 customer workspaces were accessed without authorization (1 code-signing certificate file whose password the attacker could not access, 1 provisioning profile and 13 diagnostic build logs from May 2026), and Bitrise recommends customers rotate stored secrets and reconnect GitHub as a precaution.

Activity for this story

Current comparable activity
6
Peak comparable activity
10Nov 20 03:00
Change in the past 24 hours
–

Trends compare the same fully observed participants, which may cover fewer participants than current activity. Move the pointer or tap the chart to inspect hourly activity; use the left and right arrow keys with a keyboard.