Shared document

Source

Summary

198.244.216.51 connects the first Bewitt burst, targeted probes on Konnect Kit, the tagged Emergent Accounts and eSports traffic, and the busiest sampled Tellenze login window. It also made two homepage requests to Bakkerij Broodhuys. The timing and repeated use of one client address show activity across several properties. The logs establish an address and sequence of requests. The operator and motive are unknown. [Incident work item]

The owner reported automated form submissions increasing email bounces and repeated Emma use consuming OpenAI credits. This review counts origin requests and persisted markers. Email delivery and OpenAI usage totals were outside the reviewed logs.

Timeline

Times are CET (UTC+1). The investigation uses retained logs from 4 November onward for the named sites. The last targeted check was 18 November at 01:48:47 CET.

TimeObservation
Mon 16 Nov, 06:34A different source probed /.env on both static sites before the Bewitt burst. Routine curl scans were already visible on both sites on 10 November.
Mon, 20:32:11–20:55:51First linked Bewitt burst. The client sent HEAD /, then private-file probes, followed by requests to login, account creation, event, and Emma routes. 770 requests in 24 minutes.
Mon, 21:12:54First matched Konnect Kit request, a curl GET /. The same IP probed private paths on Tuesday from 01:57:45 to 07:56:25.
Mon, 22:02:32 and 22:20:50First literal artex marker in a Bewitt event URL, followed by the first stored custom quote request with an @artex.invalid address.
Tue 17 Nov, 02:19:15 and 02:19:45The linked IP made two successful homepage requests to Bakkerij Broodhuys.
Tue, 03:42:31–19:49:08Bewitt recorded 25,576 requests to application write routes via Cloudflare's shared cross-zone Workers address. Artex markers appeared in Worker URLs or referrers from 04:32:22. The first tagged demo submission was stored at 08:07:48. The first successful organizer API sign-in under investigation was at 09:53:18.
Tue, 17:20:36 and 17:20:55Emergent Accounts stored two @artex.invalid registrations. The origin logged POST /register → 201 with bare Mozilla/5.0 at both timestamps.
Tue, 17:31:20–18:35:17Emergent Accounts logged 1,610 requests carrying the exact Linux ArtexCanary user agent. An eSports sign-in redirect at 17:38:33 carried the same string. Cloudflare recorded 1,595 matching Accounts requests and one eSports request, all from the linked IP.
Tue, 17:33:05–Wed 18 Nov, 01:48:11Tellenze workspace discovery began at 17:33:05. The first rejected password request was at 17:35:02 and the sustained burst began at 17:49:35. The origin logged 8,442 password POSTs through the last recorded attempt. The 18:15–18:30 peak had 1,302 at origin and 1,293 matching edge records from the linked IP.

Targeted paths and responses

Bewitt

Monday's 770-request client burst included 44 private-path probes (40 returned 404 and four 403), including GET /.env, GET /.git/HEAD, and GET /.git/config. The same burst reached POST /login 34 times, POST /events/private 10 times, and POST /emma 15 times (13 HTTP 200, two 419). It also reached the participant and organizer login routes, password reset initiation, and event-account creation.

The following Tuesday counts are for selected routes at the shared Worker address, 03:42:31–19:49:08 CET. Path parameters represent IDs or slugs. Counts are HTTP responses to requests.

AreaMethod and pathRequests and statuses
Admin API loginPOST /api/admin/login9,494. 8,323 × 422, 1,169 × 429, one 302, one 404.
Organizer API loginPOST /api/organizer/login6,470. 6,043 × 422, 384 × 429, 40 × 200, three 404.
Organizer web loginPOST /en/organizers/login5,781. 5,771 × 302 and 10 × 419.
Participant loginPOST /participant/events/login1,572. 1,554 × 302, 15 × 419, three 422.
Signup and resetPOST /join, POST /en/events/create/account, POST /password/email108, 60, and 35, respectively. Responses were mostly redirects.
Emma chatPOST /en/emma, POST /emma108 combined. 74 × 200, 27 × 419, seven × 422.
Demo and quote formsPOST /en/demo, POST /custom-quotes6 demo requests returned 302. 7 quote requests returned six 302 and one 419. Separately, the database contained six tagged demo submissions and three tagged quote submissions across the incident.
Event creation and editsPOST /en/events, POST /en/events/private, PATCH /en/organizers/events/[event]/experience46, 34, and 65, respectively.
Member and participant operationsPOST /api/organizer/organizations/[id]/members, POST /api/organizer/events/[id]/participants66 and 28. The first returned six 201 and the second 17. The counts describe HTTP responses.
Event supportPOST /en/organizers/events/[event]/support38. 37 × 302 and one 419.

The organizer investigation associated 37 token issuances with the affected pre-existing organizer account and verified containment. The reviewed Worker window contained zero admin API login HTTP 200s. [Bewitt account investigation]

Emergent Accounts and eSports

The Accounts origin totals below are for the 1,610 exact ArtexCanary records, plus the two signup anchors where specified.

Method and pathObservation
POST /registerTwo timestamp-matched 201s for the stored tagged registrations. Both carried bare Mozilla/5.0 before the ArtexCanary burst.
POST /login1,473 in the tagged cohort. 1,415 × 422, 47 × 429, 11 × 200.
PATCH /settings/profile10. Seven 302s and one each of 419, 422, and 423. Seven tagged profile updates were recorded in the app audit.
POST /user/confirm-password3, all 201.
POST /email/verification-notification2, one 202 and one 419. Repeated reads also checked verification, profile, and token settings routes.
GET /auth/emergent on eSports1, a 302 sign-in redirect with the same user agent and client IP.

Rate-limited and rejected responses account for 1,462 of 1,473 tagged login POSTs. The Accounts case records what could be established about the unverified users and successful responses. [Accounts incident], [Cloudflare Accounts and eSports query]

Tellenze

Method and pathObservation
POST /workspaces/find on the platform88 from 17:33:05 to 20:56:41. 41 × 429, 20 × 422, 27 × 302.
POST /auth/password on workspace hosts8,442 from 17:35:02 to 01:48:11. 8,205 × 422, 170 × 429, 63 × 302, three 419, one 404.

The three retained sessions matching the peak IP and exact Chrome user agent were unauthenticated. The privacy logs omit account identity and leave the outcomes of the 63 redirects unresolved. Those logs also omit source IP and user agent. The one-IP result applies to the 18:15–18:30 Cloudflare window. [Tellenze edge peak]

Static sites and other properties

  • Konnect Kit. 64 matched-source requests, including 13 private-path probes. Eleven returned 403 and two 404. The source used curl/8.18.0 eight times and also sent browser-shaped user agents. The baseline includes 393 curl probes on 10 November.
  • Bakkerij Broodhuys. Two matched-source GET / requests returned 200, both using a Windows Chrome 126 signature. Another source probed /.env and /.git/HEAD earlier on Monday. Their 200s were consistent with the static homepage fallback. Both filenames were absent from the served directory at inspection. The access logs contain no response body for those historical requests.
  • Neither static site logged a literal Artex marker in the reviewed baseline and incident window (18,749 Konnect Kit origin entries and 48,933 Bakkerij entries). The linked source also made 14 Emergent public site requests and one request to Comms. BLCKMKT, Cosmocrafter, and Parallaxy showed generic scans in the additional-vhost screen starting 15 November at 18:00.

User agents and high-volume addresses

Observed user agentEvidence
curl/8.18.0680 of 770 requests in the first Bewitt burst and 8 of 64 from that IP at Konnect Kit.
Mozilla/5.0 (bare)89 of 770 in the first Bewitt burst, 12 of 64 at Konnect Kit, and on the two successful Accounts signup responses at the recorded timestamps.
Mozilla/5.0 (X11; Linux x86_64) ArtexCanaryAll 1,610 tagged Accounts origin requests and the eSports redirect. The Emergent zone retained 1,596 total edge matches from the linked IP, of which 1,595 were at Accounts and one was at eSports.
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36All 1,293 matching Tellenze edge rows at the peak. Also on 19,490 of 25,576 Bewitt Worker-source requests to application write routes, including 33 of 40 successful organizer API login responses. A user-agent string alone is weak attribution.

A client IP qualifies for the list when it has at least 100 relevant requests within one verified window.

AddressObserved volume
198.244.216.51770 Bewitt origin requests Monday 20:32–20:55. 1,595 Accounts edge matches Tuesday 17:30–18:36 plus the eSports redirect in that window. 1,293 Tellenze edge matches Tuesday 18:15–18:30. The 64 Konnect Kit requests and two Bakkerij homepage visits corroborate the address match.

Accounts logged the Cloudflare edge peer in both Apache address fields for the tagged requests. Its origin grouping could not establish the client IP. The dashboard's source-IP field directly confirms the link that was missing in the initial origin-only comparison. Edge and origin totals overlap and are reported separately.

Bewitt's 2a06:98c0:3600::103 entries use Cloudflare's fixed address for cross-zone Worker subrequests. The defined Tuesday window has 44,798 total requests at that address, including the 25,576 requests to application write routes. The historical upstream Worker zone remains unknown. [Cloudflare Worker IP reference], [Bewitt edge query]

Evidence and limits

  • Main origin survey covered 244 current and rotated files and 1,722,778 lines. The targeted path and user-agent pass re-read the relevant rotations. Origin evidence anchors include bewitt_access.log.2.gz and .1, emergent-accounts-access.log.1, emergent-esports-access.log.1, tellenze-access.log.1, tellenze-workspaces-access.log.1 and the current log, plus the Konnect Kit and Bakkerij access rotations. Application anchors include bewitt.custom_quote_requests, bewitt.demo_requests, emergent_accounts.users, and emergent_accounts.security_audits.
  • The authenticated Bewitt Security Analytics view excludes Worker subrequests. The exact 09:51–09:56 CET organizer-login query in Observability Logs returned zero rows. The Bewitt origin log did not retain CF-Worker or CF-Ray for that request. Resolving the upstream zone requires an independently retained record with that attribution.
  • The Tellenze burst was still active at the 01:48:47 check. Subsequent activity is outside this record's cutoff.
Sent this? Manage