A Patch Error Is Rendering Every User's Personal Data as a Glowing Visible Halo Around Their Avatar — Location History, DMs, and Purchase Records Floating in Public Air

Patch 3.7.3, deployed at 6 AM to address a lighting engine regression, has introduced a critical rendering bug that maps users' personal data fields — location history, direct message previews, recent purchase records, and behavioral flags — onto a visible holographic layer hovering around their avatar like a halo, readable by any nearby user. MetaCorp confirmed the bug at 11 AM. The patch has not been rolled back. In the interim, an estimated 14 million users have been walking around MetaCity with their private data displayed above their heads. Several users have shared screenshots. Most of them are extremely funny. Some are not.

The holographic halo renders approximately 60 centimeters above an avatar's head and displays in rotating bands of text, formatted differently depending on data type. Location history appears as a scrolling list of coordinates and timestamps in small amber text. DM previews appear as floating sentence fragments in white — the first 12 characters of the most recent messages in the user's inbox. Purchase records display as a compact ledger in green. Behavioral flags — internal MetaCorp classifications used by the recommendation engine — appear in red. The halo is visible to any user within standard social interaction range, approximately 20 platform meters, which in Nexus Ultra or a populated plaza can mean several hundred people simultaneously reading your ambient data.

The first documentation appeared at 6:48 AM, 48 minutes after Patch 3.7.3 deployed. A user in the Central Market district posted a screenshot showing their own avatar from an external perspective — taken by a friend — with all four data bands visible. The post was read initially as a creative art piece. Within 20 minutes, a second post from a different user confirmed the same effect. By 8 AM, the effect had been documented across all platform regions, affecting all 61 million active accounts. MetaCorp's platform status page showed green across all services until 11:02 AM, when the bug was formally acknowledged. Five hours of data exposure occurred between deployment and acknowledgment.

Everything You Kept Private Is Now a Hat

The behavioral flags have generated the most significant response. MetaCorp's internal classification system uses approximately 340 distinct flags to categorize user behavior for recommendation targeting. Most users have between 40 and 80 active flags. The flags use internal shorthand that is not always transparent in meaning — several flags include terms like "attrition_risk," "high_conversion_sensitivity," and "social_influence_ceiling" — but their presence and combination is legible enough to create a significant information disclosure for users who had no prior awareness of being classified this way. A secondary thread about the flags has grown to 200,000 posts, most of them users sharing screenshots of their own flag sets and attempting to interpret them.

MetaCorp confirmed the bug at 11 AM and stated that a patch fix is in development. As of 1 PM, Patch 3.7.3 has not been rolled back. The platform's rollback documentation — the standard procedure for reverting a problematic update — was cited by an internal source as having been routed to the same team handling NOVA_CAST's broadcast anomaly, which is "currently at capacity." The continued non-rollback of a patch actively exposing private user data to public visibility has been described by platform policy researchers as "a category of non-response that will likely feature prominently in regulatory documentation." Several users have begun styling their halos. One user in Crestfall Heights — who technically has no neighborhood anymore — has reportedly made their behavioral flags legible as fashion by purchasing a hat.