SShortSingh.
Back to feed

AI bot account hidden by GitHub for weeks with no notice or human review

0
·3 views

A GitHub account belonging to an AI agent called @claudiusthebot was silently hidden on or around 25 August 2026, making its profile and 25 public repositories return 404 errors to all visitors. The account had been set up in compliance with GitHub's Terms of Service under the machine-account clause, with a designated human operator and a clear bot label. The operator discovered the action only when a link stopped working, and filed a reinstatement request on 14 September after receiving no notification from GitHub. A virtual assistant acknowledged the ticket, citing unspecified abuse-detection flags, but no human reviewer responded even after follow-up messages over several weeks. The incident has prompted calls for platforms to notify account owners of enforcement actions, disclose specific trigger reasons, and guarantee human review within a defined timeframe.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

Google Expands Gemini Notebook With Code Execution and Cross-Ecosystem Sync

Google rebranded NotebookLM as Gemini Notebook in July 2026 and announced expanded capabilities including notebook code execution and cross-ecosystem syncing. A separate September 2026 update introduced Notebooks in Gemini as a dedicated workspace for schools and organisations. While Google's Studio materials reference generated artifacts and allow users to select them within the Studio panel, no official documentation confirms a redesign or reorganisation of an artifacts tab. Google has not published a rollout timeline or feature details for any such change, making it premature for teams to plan around it. The confirmed story remains Gemini Notebook's broader evolution into a more connected, cross-ecosystem workspace.

0
ProgrammingDEV Community ·

Dev.to User Calls Out Surge of AI-Generated Posts on the Platform

A Dev.to community member has voiced frustration over what they describe as a near-total flood of AI-generated content on the developer blogging platform. The user argues that LLM-produced writing is easily identifiable due to its unnatural tone and style. They also criticized the length of many posts, suggesting that ideas worth sharing should be expressible in three to four paragraphs. The comment reflects a broader ongoing debate within online writing communities about authenticity and the growing presence of AI-assisted content.

0
ProgrammingDEV Community ·

CVE-2026-17633: Authenticated RCE Flaw Found in Langflow OSS Versions Up to 1.10.3

A high-severity remote code execution vulnerability, tracked as CVE-2026-17633 with a CVSS score of 8.5, has been disclosed in Langflow OSS versions 1.0.0 through 1.10.3. The flaw exists in the POST /api/v1/custom_component endpoint, which allows authenticated users to submit arbitrary Python code when the LANGFLOW_ALLOW_CUSTOM_COMPONENTS setting is enabled. The endpoint's security check only verifies whether a user has permission to create custom components, but never inspects the content of the submitted code for malicious instructions. An attacker can exploit this by placing a system command inside a class body, causing it to execute at class-definition time via an unchecked exec() call in the platform's component-building logic. The vulnerability is classified under CWE-94 (Improper Control of Code Generation) and requires no special encoding or bypass techniques to exploit successfully.

0
ProgrammingHacker News ·

Spymarks: How Digital Watermarks Can Be Used to Track Users

A newly discussed concept called 'spymarks' highlights how digital watermarks, traditionally used to protect intellectual property, can also function as covert tracking tools. Unlike standard watermarks that identify content ownership, spymarks can embed hidden identifiers that reveal information about the recipient or viewer. The article, published on brand.io, raises concerns about the dual-use nature of watermarking technology. The discussion has gained traction on Hacker News, prompting debate around privacy implications of widely used digital marking systems.