Scope and findings
The origin review covers Monday 16 November 2026 at 18:00 through Wednesday 18 November at 03:00 CET. The end time is excluded. It processed 601,065 HTTP requests in 222 current and rotated Apache files across 40 virtual-host groups with traffic. For addresses with a recorded login failure, the lookback starts 4 November at 00:00 CET in the available logs.
Bewitt alone recorded 57,040 requests from 2,044 distinct recorded addresses. That consists of 2,043 public address values and Cloudflare's shared cross-zone Worker address. The address inventory has no request-volume threshold. The expanded Emma count is 141 chat submissions and 411 requests across Emma-related routes. [Incident work item]
Across the products, the origin recorded 27,161 failed requests on login or authentication callback routes. The investigation traced 18 distinct client IPs with a failure in the origin logs or the scoped Cloudflare queries, including addresses with a single failed request. All 18 also appear in the retained origin logs. Several had activity on another product before or after the recorded failure.
The owner reported email bounces from form spam and OpenAI credit use from Emma. The HTTP evidence measures requests and responses. It does not contain send results or model billing.
Timeline and source pivots
All times in this section are CET. The first direct Bewitt burst, the larger tagged Accounts wave, and the Tellenze password wave share the observed client IP 198.244.216.51. The IP is a network observation. The operator and motive are unknown.
| Time | Observed activity |
|---|---|
| Mon 16 Nov, 13:31–17:14 | One IPv6 address later seen on rejected Bewitt login requests already made 273 origin requests to Bewitt before the incident window. The earlier traffic belongs in the trace and does not establish an earlier attack. |
| Mon, 20:32:11–20:55:51 | Bewitt logged 770 requests from 198.244.216.51, including 44 private-file probes, 15 Emma chat submissions and seven failed login requests. The first recorded login failure was at 20:34:58. |
| Mon 20:58 through Tue afternoon | Additional addresses sent login probes and visited Emma or other paths. One address made 391 Bewitt requests on Monday with no recorded login failure there. It later returned two 404s on Tellenze Plugins at 20:04:48 and 20:05:38 Tuesday, on POST /login and GET /oauth/callback. |
| Mon, 21:12 onward | 198.244.216.51 reached Konnect Kit. It made 64 origin requests, including 13 private-file probes that returned 403 or 404. It later made two successful homepage requests to Bakkerij Broodhuys at 02:19 Tuesday. The two static sites had scanning before this burst from different addresses. |
| Mon, 22:02 and 22:20 | First explicit Artex string in a Bewitt event URL and first stored @artex.invalid quote request. Bewitt stored three tagged quotes and six tagged demos during the reviewed incident. |
| Tue 17 Nov, 03:42–19:49 | Bewitt saw 25,576 requests to application write routes in the earlier Worker cohort, including auth, event and member operations, forms, and chat. Across the entire expanded window the shared Worker address accounted for 45,064 origin requests and 15,972 login failures. |
| Tue, 17:13–17:49 | The linked IP reached Tellenze at 17:13:26 in the origin logs. It appeared at Emergent Apps, eSports, Emercy and Rewards from 17:26:05 at the edge, before the sustained Tellenze password burst. Accounts stored tagged registrations at 17:20:36 and 17:20:55. Tellenze workspace discovery spiked at 17:33:05 and the first origin password failure was at 17:35:02. |
| Tue, 19:07–20:24 | A second source that had nine failed Bewitt logins on Monday made 30 Emercy requests between 19:07:02 and 19:22:15 Tuesday and one request to the Emergent public/shared vhost. Another source made 17 requests on that vhost at 20:22:11–20:22:15 and then received a 429 on Accounts at 20:24:42. |
| Tue, 18:40 and Wed 01:02 | Matching Cloudflare rows resolved two Apps callback 500s and three eSports callback 400s to two additional addresses. The Apps address visited the Emergent public/shared vhost and Emercy earlier, then made 18 Blackstar Drift requests after the errors. The eSports address had Emercy and Emergent public/shared vhost activity before the errors and further public/shared vhost activity afterward. |
| Wed 18 Nov, 02:59 | The last visible edge failure for the linked IP was at 02:59:21 on Tellenze and 02:59:26 on Accounts. Both were still recording failures near the 03:00 cutoff. |
The 391-request address had activity on Bewitt and later on Tellenze even though Bewitt recorded zero login failures for that address. Checking only IPs with failures on Bewitt would have missed it. The two Apps and eSports callback sources illustrate why a single login error is tracked as an investigative lead. [Tellenze alternate login routes], [Apps callback sample], [eSports callback sample]
Bewitt · Emma and other targeted areas
The previous report's 108 Emma chat submissions were for Cloudflare's shared Worker source alone. This revision counted every recorded source and checked the deployed chat route declarations, including the localized routes, at routes/web.php:187–190.
| Chat submission path | Origin POSTs | HTTP responses |
|---|---|---|
/emma | 75 | 49 × 200, 22 × 419, four 302. |
/en/emma | 66 | 48 × 200, 11 × 419, seven 422. |
/use-bewitt/emma and locale-prefixed variants | 0 | Deployed route, with no matching POST in the window. |
| Total | 141 | 97 × 200, 33 × 419, seven 422, four 302. |
The 141 POSTs came through three recorded source values. 108 used the shared Worker address, 15 came from 198.244.216.51, and 18 came from a second public address with a failed Bewitt login. The 411 broader Emma requests also include session requests, about-page accesses, admin history reads, and requests using unsupported methods. A chat HTTP 200 measures an HTTP response. The number of provider calls and charges is unknown.
| Other targeted area | Recorded evidence |
|---|---|
| Admin API login | POST /api/admin/login returned 8,323 responses with 422 and 1,169 with 429. The origin also recorded a 404 for that method and path. |
| Organizer API login | POST /api/organizer/login returned 6,043 responses with 422, 384 with 429, and three with 404. |
| Organizer web and participant login | POST /en/organizers/login returned 17 × 419 and 14 × 422. POST /participant/events/login returned 45 × 419 and three 422. |
| Signup and forms | The origin recorded requests to /join, /en/events/create/account, /en/demo, and /custom-quotes. The earlier Worker route breakout had 108 on POST /join, 60 on POST /en/events/create/account, six on POST /en/demo, and seven on POST /custom-quotes. |
| Event operations | The Worker route breakout also recorded requests to POST /en/events, POST /en/events/private, PATCH /en/organizers/events/[event]/experience, and API member and participant routes. |
| Static and configuration-file paths | The first direct Bewitt burst probed /.env, /.git/HEAD, and /.git/config. All 44 configuration probes in that burst returned 403 or 404. |
Failed logins across the products
A failed HTTP login or identity callback request is recorded as an intrusion attempt for this investigation. The count includes observed 4xx and 5xx responses on sign-in submissions and identity callbacks, including rejections, throttles, unsupported login paths, and application errors. These categories carry different evidentiary weight. A 302 redirect by itself gives no failure verdict, so it remains unclassified. This matters for Bewitt's 7,723 login-route redirects. A page view of a login form is counted as traffic.
| Origin group | Intrusion attempts | Evidence |
|---|---|---|
| Bewitt | 16,043 | 2,044 recorded source values across all traffic. The shared Worker value accounts for 15,972 failures. Five public addresses account for the remaining 71. |
| Tellenze workspaces | 8,793 | Password login, other sign-in attempts, and callback errors. The workspace HTTP privacy log omits source IP on those failures. |
| Tellenze platform | 1 | POST /auth/password returned 404. |
| Emergent Accounts | 2,316 | Rejected POST /login requests. The origin retained Cloudflare peer addresses for these failures. |
| Emergent eSports | 4 | Identity callbacks returned 400. |
| Emergent Apps | 3 | Two identity callbacks returned 500 and one returned 404. |
| Emergent Rewards | 1 | Identity callback returned 404. |
| Total | 27,161 | Retained origin requests across the reviewed streams. |
The edge checks provide client addresses where the origin could only count the event. Edge and origin results can describe the same request and should be read as separate views of the traffic.
- Bewitt. Cloudflare showed 488 failed POSTs from 14 client IPs on the five checked login paths. Two IPv6 addresses in one prefix accounted for 279 and 119 records. Their visible samples were all edge 403s. Several addresses reached both layers. The raw-IP timeline records timestamps where the UI showed them. For the two largest IPv6 groups the earliest timestamp is from the visible row sample. [Cloudflare Bewitt login query]
- Emergent Accounts. Cloudflare showed 2,298 failed
POST /loginrequests, with 2,297 from198.244.216.51and a single 429 from a second source. The earlier, exact ArtexCanary cohort accounts for 1,610 Accounts origin requests across routes, including 1,462 rejected login POSTs. The expanded edge check covers the full window and all user agents. [Accounts edge query], [Accounts work item] - Tellenze. Cloudflare recorded 8,800 failed or aborted
POST /auth/passwordrequests, all from198.244.216.51. The targets were Bewitt workspace 4,591, demo workspace 2,109, Tellenze workspace 2,089, apex 10, and admin 1. Statuses were 8,615 × 422, 169 × 429, 11 × 404, three 419, and two 499. There were 12 more edge failures on other checked login or callback paths, ten from the main address and two from the address seen on Bewitt the previous evening. [Password failure query], [Other Tellenze login paths] - Other products. The linked IP made 3,217 requests at the Accounts edge, 29 at Apps, 27 at eSports, 25 at Emercy, 18 at Rewards, 14 at the Emergent public site, five at Newsroom, and one at Comms. The host-specific checks found callback errors at Apps, eSports, and Rewards. Tellenze also logged the same source on workspace discovery, MCP, and plugin OAuth paths. These counts describe requests to those surfaces. [Emergent linked-source query], [Tellenze linked-source query]
User agents
| Observed string | Evidence |
|---|---|
curl/8.18.0 | 680 of the 770 first-wave Bewitt requests and eight of the 64 Konnect Kit requests from the linked IP. Across all Bewitt origin traffic in this window, this exact version appeared 1,606 times. |
Mozilla/5.0 | Bare string on 89 requests in the first Bewitt burst and on the two Accounts registration responses at the stored timestamps. |
Mozilla/5.0 (X11; Linux x86_64) ArtexCanary | Exact string in the 1,610-request Accounts origin cohort and the eSports sign-in redirect at 17:38:33 Tuesday. |
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36 | The exact string at Tellenze's linked 18:15–18:30 peak. It appeared on 19,490 of the earlier 25,576 Bewitt Worker application-write requests, and on 36,146 Bewitt origin requests overall in this revision. The string is a supporting indicator when combined with the observed route, address, and time. |
Evidence files and logging limits
Omicron-address-inventory-2026-11-18.csvis in the local incident workspace. It has 10,510 product and source rows, including all 2,044 source values observed at Bewitt origin. Rows with a blank address represent logs that omit it. Each row has its request count, failure count, Emma volume, first and last seen times, and observed user-agent families or exact strings.Omicron-failed-login-IP-timeline-2026-11-18.csvis in the same workspace. It has 85 evidence rows for all 18 identified client IPs. It includes product, before/after observations, timestamped failure anchors, and the precise Cloudflare query where applicable. Both CSVs use UTC timestamps.- Files include
bewitt_access.logand its rotations,tellenze-access.log,tellenze-workspaces-access.log,tellenze-custom-domains-access.log, and logged address or privacy streams for Accounts, other Emergent products, the games, and static sites. The final origin pass parsed all timestamped rows in the incident window with zero read errors or observed rotation during the pass. - Several products log an edge peer or omit client addresses, paths, or both. The full Bewitt edge traffic view exposed a top-20 IP list and 50 request rows. A complete edge-only address inventory is unavailable from the views used here.
- Cloudflare's
2a06:98c0:3600::103is a shared cross-zone Worker address. Its volume cannot identify one client. Bewitt Security Analytics excludes Worker subrequests, and the historical organizer-login query returned no matching row in Observability Logs. The origin did not retain the Worker header or Ray ID for that request. The Worker zone therefore remains open. [Cloudflare Worker header documentation], [Bewitt incident record]