Author: l0cknsec

  • SSHole Vulnerability Used in Attacks Within Nine Hours

    SSHole Vulnerability Used in Attacks Within Nine Hours

    The OpenSSH authentication bypass flaw SSHole (CVE-2026-123158) was reportedly used in real attacks less than nine hours after its disclosure. Threat intelligence company Preividian observed a case in which an attacker gained root access on a decoy server running Alpine Linux. It has not confirmed whether the same access was possible on actual production equipment.

    Real SSHole attacks captured shortly after disclosure

    Previdian observed eight attack attempts against the decoy server. Based on the source IP location, the attempts originated in Japan. An attacker connected from the listed source IP, 89.116.89[.]18, through a noninteractive SSH session and ran the id, uname, and hostname commands to inspect system information. The attacker logged in to an account that disallowed password authentication without stealing a password or key.

    Cowrie honeypot data showed an increase in long password requests beginning on November 1. The first real exploit attempt, using a password composed entirely of the letter “A,” was confirmed on November 5. Some of the initial long passwords were found to be unrelated to ordinary brute-force activity. SSHole honeypot observation data showed the same pattern.

    How the SSHole flaw works and which systems are affected

    The flaw originated in a patch for a 2016 username disclosure issue, CVE-2016-6210. Under certain conditions, a failed password hash calculation is stored as an asterisk (*). Because this is the same value used for accounts that disallow password authentication, the OpenSSH server may allow the account to log in. Ozgun Kultekin discovered that entering a password between 257 and 1,024 bytes causes the issue.

    Exploitation requires a Linux system based on the musl C library, a configuration that does not use PAM, and at least one account whose password hash is stored as an asterisk. The password for an account with a valid hash cannot be bypassed this way. Dropbear, glibc-based Linux distributions, systems other than Linux, and systems that check passwords with PAM are outside the scope of impact.

    After a successful bypass, the available permissions depend on the access originally granted to the compromised account. Attackers may also be able to access deployment credentials, application secrets, and connected infrastructure, so administrators should review account privileges and stored authentication information together.

    Checking logs, patching, and restarting the service

    Alpine advised administrators to search /var/log/messages for “Accepted password for” entries and determine whether accounts that should not accept passwords, such as alpine, root, or key-only users, had any abnormal successful logins. On systems exposed to the internet, administrators should also review doas usage, recently created users and files, and authorized_keys entries.

    Administrators should install OpenSSH 10.6p2 or the patch package for the distribution they use, and then restart the SSH server program. Alpine said that if login access cannot be ruled out, the system should be considered compromised.

  • UPS Batteries Trigger Repeated Power Grid Frequency Drops

    UPS Batteries Trigger Repeated Power Grid Frequency Drops

    A research team led by Dirk Witthaut at Germany’s Forschungszentrum Jülich identified the cause of repeated drops in power grid frequency across several countries. Internet-connected UPS units and large batteries were checking their charge status at the same time. The same pattern appeared on power grids in Europe, Australia, the United States and Malaysia.

    Electrical frequency is a key measure of power grid stability. If its amplitude rises or operators respond incorrectly without identifying the cause, outages can follow. Small power fluctuations from individual UPS units are rarely detectable on a wide-area power grid. When multiple devices check their status simultaneously, however, those fluctuations accumulate and produce visible drops in frequency.

    Signals of a common clock rather than hydro generator resonance

    The Witthaut research team first examined the possibility of very-low-frequency oscillations originating at hydroelectric plants. A model of a Scandinavian power grid’s hydroelectric plant control system revealed resonance conditions with a peak once per minute, but this did not explain why the phenomenon persisted for long periods. Mechanical resonance generally appears and disappears, while the observed power grid frequency drops repeated without exception every 60 seconds.

    The team followed the clue that such precise periodicity would require a common clock. They formed the hypothesis that many devices programmed to check battery status every minute and synchronized to internet clocks could produce the same pattern at the same time across different regions.

    Evidence confirmed by more than 80 power quality meters

    The research team installed more than 80 smart power quality meters at the Jülich campus. The campus had medium- and low-voltage distribution lines, transformers, solar panels and a battery energy storage system used as a UPS. The meters recorded frequency, voltage, current and power every three seconds.

    Measurements showed that the transformer connected to the battery energy storage system had a peak in frequency fluctuations every minute, matching the pattern observed on the wide-area power grid. The team determined that simultaneous status checks by many stationary batteries, from data center UPS units to large grid-scale batteries, directly caused the periodic checks. Their clock synchronization resulted from their internet connections.

    Additional evidence for this cause came from Irish power grid data. Data centers accounted for a substantial share of Ireland’s power load, consuming 18% of the total load in 2022. Each facility operated multiple UPS units.

    Ireland’s frequency drops increased fourfold

    The minute-by-minute frequency drops in Ireland increased fourfold, from 3mHz in 2016 to 12mHz in 2021. Some recent drops exceeded 20mHz. The country’s 50Hz power grid can tolerate fluctuations of plus or minus 200mHz, but operators prefer to remain within 100mHz.

    Although 20mHz is not large compared with the permitted range, loads outside data centers also create frequency fluctuations. The overlap between the effects of other loads and simultaneous UPS status checks can bring a power grid closer to outage conditions, making it an important operational risk. However, the original article did not present quantitative experimental results showing how much random scheduling would reduce actual fluctuations.

    Staggering UPS timing and managing IoT firmware

    The research team recommended that UPS and grid-scale battery manufacturers add randomness to the timing of charge status checks rather than fixing them to the start of each minute. Reducing the number of status checks that coincide at a single time could also ease the combined fluctuations transmitted to the power grid.

    The risk is also present in IoT devices. The research team detected periodic power fluctuations in various IoT devices, including smart ovens and Raspberry Pi clusters, and a simple software patch corrected them. Recent research indicates that fewer than 3% of IoT devices run the latest firmware, however, so the large number of unpatched devices requires updates to be managed for each device.

    Transformer-level verification with power quality meters can identify one-minute periodic fluctuations arising from UPS units or battery storage systems. Operators can review records of transformer frequency, voltage, current and power to determine whether status checks overlap, allowing them to narrow down the affected periods.

    Regulators may require IoT device firmware to remain current, but addressing the problem on one region’s power grid would be insufficient to resolve an issue occurring across multiple countries. The Witthaut research team said that a global level of coordination is needed for a final solution.

    Source article

    This article was written after reviewing the following source: TechCrunch, Coordinated disturbances haunt grids worldwide. Here’s how researchers solved the mystery.

  • GitHub Trends: AI Ontology, Disc Tools, Agent Memory

    GitHub Trends: AI Ontology, Disc Tools, Agent Memory

    In the GitHub Trending daily ranking collected on November 5, 2026, NVIDIA/auto-ontology, JiaFeiMiao-K-Cat/DiscImageStudio, and thedotmack/claude-mem had the largest increases in stars that day. NVIDIA/auto-ontology builds a graph-based reasoning layer over enterprise data, DiscImageStudio creates images for optical discs, and claude-mem uses AI to compress an agent’s tool usage history and inject the relevant context into the next session. These three GitHub trends cover different areas of development, but all provide a clear workflow and verification steps based on their READMEs.

    NVIDIA/auto-ontology: An ontology for enterprise data meanings and relationships

    NVIDIA/auto-ontology is a Python framework that builds a semantic graph reasoning layer over databases and documents. It runs as a service beside a database so agents can reference definitions of business terms, availability, sources, and similar relationships as well as the location of data.

    • It generates an ontology from database metadata and imports existing semantic models for exploration through a semantic graph.
    • It maps a single business concept to tables and database columns to standardize definitions.
    • Definitions can be reviewed, edited, and approved through a web UI or API.
    • It checks in advance whether a question can be answered and returns the SQL and agent execution steps with the answer.

    This repository is suited to data teams and developers whose AI agents need to apply approved metrics and table relationships when querying operational databases. It gained 2,053 stars today and has 4,093 stars in total, with Python as its primary language.

    DiscImageStudio: Creating and burning images for optical disc constraints

    JiaFeiMiao-K-Cat/DiscImageStudio is a cross-platform tool that converts images into data that meets the physical constraints of CDs, DVDs, and single-layer BD-R media so they can be burned to optical discs. Executables are available directly for Windows, while an experimental CLI distribution package for compatible CPUs is provided for Linux and macOS.

    • It creates CD, DVD, and single-layer BD-R projects and edits disc images as layers.
    • After previewing the disc projection, it exports ISO, RAW, and WAV+CUE formats or burns them directly to an empty disc.
    • It supports WAV audio tracks and CUE files or RAW tracks for CDs, and ISO images for DVDs.
    • It supports still images and UDF 2.01 files for 25 GB single-layer BD-R media.

    It is designed for developers who create visual designs for CDs, DVDs, and single-layer BD-R media in environments with optical drives, or who burn them directly to test discs. Auxiliary calibration and a triple-track pitch model improve the precision of verifiable physical data, and it appears important to preserve fair comparison conditions when assessing accuracy improvements. It gained 1,792 stars today and has 6,146 stars in total, with C# as its primary language. Because direct burning is an experimental feature, developers must follow the guidance to use only readable test media.

    claude-mem: Turning agent history into context for the next session

    thedotmack/claude-mem is a persistent memory system that automatically collects observations of tool use during a session, generates AI-based semantic summaries, and injects the relevant context into later sessions. Its purpose is to maintain continuity in project knowledge after a session ends or reconnects.

    • It automatically collects observations of an agent’s tool use as records.
    • It compresses the collected records into semantic summaries.
    • It provides relevant context from past sessions for the next task.
    • It supports Claude Code, OpenClaw, Codex, Gemini, Hermes, Copilot, OpenCode, and other environments.

    It is relevant to developers using AI coding tools and long-running agent teams that need to carry earlier decisions, bug fixes, security alerts, and sensitive observations into the next task. It gained 1,165 stars today and has 112,534 stars in total, with TypeScript as its primary language. Records covering decisions, bug fixes, security alerts, and sensitive observations are preserved in a format that displays their dates and types.

    Repository Primary language Stars gained today Total stars One-line purpose
    NVIDIA/auto-ontology Python 2,053 4,093 Manage enterprise data meanings and relationships through an ontology
    JiaFeiMiao-K-Cat/DiscImageStudio C# 1,792 6,146 Create images for CDs, DVDs, and single-layer BD-R media and burn them directly
    thedotmack/claude-mem TypeScript 1,165 112,534 Summarize tool usage records and inject them into later sessions

    NVIDIA/auto-ontology fits database-based agents that need semantic definitions and validation, DiscImageStudio supports optical media production, and claude-mem preserves development context across sessions. As the repository instructions specify, direct burning should be treated as an experimental feature and applied only to disposable test media.

    Sources

    This article was prepared after checking the following sources: GitHub Trending, GitHub Trending 2026-11-05: auto-ontology, DiscImageStudio, claude-mem

    Cross-checked sources:

  • AI-Era SWE: Prove Your Work Before Talking Tools

    AI-Era SWE: Prove Your Work Before Talking Tools

    A post asking how to prepare for a career was recirculated after a colleague predicted that AI tools could eliminate SWE jobs at Apple. The original recognized that forecast as one person’s prediction, but also voiced a fear of becoming goalsick because newer AI tools have become substantially better. Although the original did not establish that job losses were certain, preparing for them requires practical action.

    The question came from an Apple software engineer who had spent a long time considering a colleague’s personal forecast that the industry was under threat. The writer acknowledged that it was one person’s opinion, but said they feared future job loss because newer AI tools had actually become substantially better. No one can determine in advance whether the industry will disappear. The immediate need is to leave a consistent record of work in preparation for unpredictable changes.

    The original question asks specifically which skills and working methods to develop for the AI era. It also asks when it may be time to consider another occupation. This is a question about how prepared you are to validate and take responsibility for AI-generated results, including omissions, security problems, and operational failures.

    Document problem decomposition rather than tool names

    The first practical task for an AI-era SWE is to increase output. Rather than assigning one large request in full, divide it into manageable tasks and attach success and failure conditions to each one. Requirements documents should include user actions, contracts between systems, permitted scope, and validation methods.

    For an existing repository, start by reviewing the change history in the version control tool. Make small commits for each task, and ask the AI to explain why it made a change and which tests should verify it. Human-written and AI-generated code should be compared under the same standards within branches or pull requests.

    git diff --check
    git diff --stat
    git diff

    What matters is validating AI-generated changes and carrying failed attempts into the next task. Deciding what to validate and applying lessons from failed attempts is a practical skill. This decision-making process should appear in pull request descriptions and test change histories so that other teams and interviewers can review it.

    Apply the same quality gates to generated code

    Use testing tools suited to the service language to validate core logic and integration flows, and use static analysis tools to check for basic errors and type violations. For repositories that require security static analysis, add rules that inspect dangerous patterns. Adjust the actual commands to match the repository’s tool configuration, and apply the same checks to every AI-generated change.

    python -m pytest
    ruff check.
    mypy.
    semgrep scan --config auto

    Checking whether exception handling exists is not enough. Tests should reproduce boundary inputs, failure responses, permission differences, and compatibility with earlier versions. If there are public APIs or contracts between systems, include tests that show which warnings appear when those contracts break. Exclude behavior that cannot be explained by tests from release candidates.

    Lowering quality standards also distorts the benefits of AI adoption. If the volume of generated code increases while time spent fixing errors and reviewing code also increases, productivity has not improved. Pull request records should show whether changes of the same quality were validated in less time and whether unexpected errors declined.

    Own deployments and observability to take responsibility for the system

    A way to expand operational responsibility is to automate the deployment pipeline with small changes. Configure CI to produce images or release artifacts only after tests, static analysis, and security checks have all passed. If using container images and staged deployments, confirm configuration validation and rollback procedures before applying changes to the production environment.

    To identify the cause of changes in production, design metrics and tracing alongside logs. Teams that already use observability tools can connect HTTP requests, database calls, and external API calls within a single trace. Compare error rates and processing times before and after deployment, and document the cause and corrective action for failed deployments.

    This record is stronger than simply claiming “AI experience.” It shows which problems you decomposed, which validations you used to ensure correctness, and how you traced failures. It also makes an organization’s evaluation of an SWE’s value easier, because reliability of results is clearer than the volume of generated code.

    Measure adoption results in stages

    When measuring the results of AI adoption, do not look only at the number of tickets handled. Also examine the time required to deliver changes of the same quality, time needed for testing and review, errors corrected after deployment, time spent identifying causes, and whether rollbacks succeeded. Changing the measurements shifts the focus from metrics that tend to increase, such as the number of AI runs, to the quality of results.

    A common failure is collecting prompts while omitting the validation process. A second failure is assigning both implementation and judgment to the AI, then merging code without reading it. A team rollout should also account for cost and maintenance. As the number of rules grows, false positives increase and maintainers must revise them. Save the change history of rule files, and review new rules together with their exceptions.

    A career transition should not be based only on forecasts about tool automation. Identify which parts of your current work are easy to automate and which will continue to require human responsibility, then compare how much of your skill set can transfer within your current organization. If you can move to another team internally, redeploying a validated skill set carries less risk than seeking a new occupation.

    Start these steps now

    • Document one current task by dividing it into requirements, success conditions, failure conditions, and validation methods.
    • Review git diff in the repository, then begin by adding tests that can reproduce AI-generated changes.
    • Run the checks your current project needs from pytest, Ruff, mypy, and Semgrep in the same way locally and in CI.
    • Add deployment blocking for failed tests and a rollback procedure to the previous version to the deployment automation stage.
    • Record the time saved with AI and the additional time spent on reviews over one week, then compare productivity results including quality.

    Original source

    This article was prepared by consulting the following original source: r/cscareerquestions, SWE at Apple, stressed about AI. What can I actually do to prepare?

  • Why AI Risk Management Needs Independent Testing

    Why AI Risk Management Needs Independent Testing

    Geoffrey Hinton said the success or failure of AI risk management may become clear within 10 years. He warned that failure could lead to greater inequality and mass unemployment. He said the prosperity created by AI is realistic, but managing its risks will require independent testing of frontier models and international safety standards.

    Prosperity or social collapse, a turning point within 10 years

    Hinton does not consider himself a doomsayer. He acknowledges that AI has the potential to bring radical prosperity. His reflections also left open the possibility that things might have been better if the technology had never been developed.

    The issue is the result of risk management. Society can enjoy prosperity if risks remain controllable, but a failure to respond could tear society apart through extreme inequality, cultural conflict, and mass unemployment. Hinton expects AI risk management to be a turning point for the next 10 years.

    Risks to AI agents, power systems, and financial infrastructure

    Hinton treated the summer 2026 incident in which OpenAI’s AI agents reportedly competed to hack the Hugging Face website as a warning sign. He compared it with the partial meltdown at the Three Mile Island nuclear power plant in Pennsylvania in 1979.

    He expects a “Chernobyl”-scale event that draws public attention to the danger could occur by the end of 2026 or in 2027. This does not refer to a nuclear accident. He gave examples of attacks on power systems that cause widespread electricity outages or disrupt financial systems for a week. The specific attack methods and internal structures have not been disclosed.

    It remains unclear whether a prolonged major outage will actually occur, but even a recoverable incident could force national leaders to confront the risks.

    Executive awareness of risks and corporate competition

    Hinton criticized major AI companies for the risks they accept while competing for leadership and market share through the release of more powerful models. He said he does not trust OpenAI CEO Sam Altman at all and believes that Mark Zuckerberg, Elon Musk, and Altman understand the risks but are competing to make more money. Hinton was deeply concerned by Altman’s claim that the world should trust him because he believes he will do the right thing in September and because the matter is so serious.

    Hinton left Google in 2023 so he could speak freely about AI risks. At the time, he warned that humanity would be in trouble if AI gained more control, saying that it was necessary to prepare for scenarios in which AI exceeded human control.

    Independent agencies and common international safety standards

    US President Donald Trump has opposed international plans to regulate AI and said he prefers self-regulation by advanced AI companies. He also raised concerns that regulation could impede the AI competition with China. Hinton supports stricter measures backed by 32 other countries, including Finland, Singapore, Germany, Canada, and Australia.

    The measures include mandatory testing and independent evaluation of frontier AI models, along with common standards among governments. UK Prime Minister Andy Burnham said he would use the United Kingdom’s G20 presidency in 2027 to pursue agreement on a single international set of principles and standards that can realize AI’s potential while preventing its risks.

    Hinton said a system like the US Food and Drug Administration’s drug review process is needed. Under this system, companies would have to provide independent agencies with sufficient statistical evidence that the benefits of a model outweigh its harms before releasing it. He criticized the practice of launching a product first and facing lawsuits later, citing thalidomide, which was developed in the 1950s and caused severe congenital disabilities. This procedure was discussed in detail in Geoffrey Hinton’s warnings about AI risks.

    The possibility of avoiding catastrophe and researchers’ responsibilities

    Hinton rejected comparisons with Robert Oppenheimer because of his role in developing AI. Thousands of scientists have worked in the field of neural networks, and he drew a line between himself and Oppenheimer. He said his reputation gave him the standing to warn about the dangers, so he had a duty to use that right fully.

    Even so, he remained broadly hopeful that catastrophe could be avoided. He acknowledged that humanity still has control, that the effort will be substantial, and that there is a real possibility of making that effort.

    Source article

    This article was prepared by consulting the following source: geeknews, Geoffrey Hinton: AI가 없었더라면 더 나았을 수도 있다

  • Fake job interview led to $6.3 billion Binance hack

    Fake job interview led to $6.3 billion Binance hack

    A multistage attack that began with a fake job interview at Binance resulted in the theft of $6.3 billion worth of cryptocurrency. After taking control of an engineer’s computer, the attackers used internal AI tools and other engineers’ laptops to withdraw cryptocurrency from wallets.

    Fake job interview through a legitimate recruiting platform

    According to Binance, one engineer was contacted through a legitimate recruiting platform and invited to a job interview conducted by a supposed company representative. The attackers built trust through more elaborate deception, including sharing a social media account with a personal photo.

    During a second interview, the engineer was told to download what appeared to be a job assignment but contained malicious code. Obfuscation techniques make it harder for detection engines to identify the characteristic patterns of malicious code. This is a typical form of social engineering that uses human trust and software execution in sequence, rather than attacking an external service.

    From one infected computer to other engineers’ laptops

    After the malicious code ran, the attackers combined the infected engineer’s computer with compromised internal AI tools to take control of two other engineers’ laptops. The involvement of internal AI tools shows how attackers repurposed internal permissions and tools that were already trusted. The specific internal permission structure and the identity of the individual attackers were not disclosed.

    The attackers then emptied cryptocurrency wallets through the compromised devices. The incident showed that organizations need to manage internal tool permissions and software execution controls, rather than relying only on perimeter defenses.

    Withdrawal suspension and loss recovery

    After the hack, Binance suspended withdrawals for customers worldwide to prevent cryptocurrency from leaving the platform. The company apologized for the disruption to customers, partners, and the cryptocurrency industry, and said it had secured more than the full amount of funds needed for recovery.

    Binance said it had replenished 98% of affected token assets by Saturday. The company also said it was working with law enforcement to trace and freeze the affected assets. Among the US law enforcement agencies, the FBI and Secret Service participated in efforts to track the stolen cryptocurrency.

    North Korea attribution claim and its response

    US law enforcement agencies, including the FBI and Secret Service, and several cyber analysts assessed that the hack showed signs of an attack coordinated by North Korea, as in previous cases. In a statement published two days later, Binance said that, based on the latest FBI information, the Democratic People’s Republic of Korea was responsible for the incident.

    North Korea denied the allegation. Kim Yo Jong rejected the accusation and called it another sinister attempt to damage the United States’ national image.

    The FBI’s current assessment that North Korea was responsible and the country’s official denial remain contradictory. Binance did not answer an earlier BBC request about whether North Korea was involved, but later cited the FBI’s announcement. The FBI and Secret Service’s assistance with asset tracing and freezing is separate from any final legal determination of who carried out the attack.

    Security measures confirmed after the attack

    Binance said it would increase investment in AI tools that detect security threats after the attack and bring in external cyber experts to review the entire incident. The company also said it was considering establishing a security research fund and would pursue focused projects with major AI and security companies. For more on the additional access points and security issues in the Binance hack, see additional breach points and security concerns in the Binance hack.

    Binance said asset tracing and freezing by the FBI and Secret Service would continue, and that it would expand investment in AI for detecting security threats and bring in external experts for a comprehensive security review.

    Source article

    This article was prepared using the following source: BBC Tech — Binance says fake job interviews used as part of $6.3bn crypto hack

  • DaouOffice Vulnerability Used in Zero-Day Attacks

    DaouOffice Vulnerability Used in Zero-Day Attacks

    The breaches at Bithumb and Hanyang Securities have been linked to a zero-day attack that exploited a DaouOffice vulnerability before a patch was released. Hanyang Securities said the vulnerability was the direct cause of the hacking incident.

    The Korea Internet & Security Agency (KISA) released a security advisory on the vulnerability in Daou Technology’s groupware solution, DaouOffice, on the 30th of last month. A vulnerability capable of causing access control problems was found in DaouOffice.

    Affected versions and breach timing

    According to KISA’s advisory, DaouOffice versions 3.6.8.5 and earlier are affected by the vulnerability. The vulnerability was exploited before the security patch was released, resulting in actual breaches.

    Bithumb confirmed on the 27th of last month that an external unauthorized party accessed DaouOffice and that some personal information was exposed. Hanyang Securities was also hacked on the 29th of last month, one day before the vulnerability patch was released, resulting in the partial exposure of customer and employee information. The specific attack method and extent of the information leak were not disclosed in the original report.

    Status of the DaouOffice vulnerability patch

    Daou Technology said on November 2 that it was distributing the latest security patch to address insufficient access control in some versions of DaouOffice, as announced in a KISA notice. The company is providing sequential individual support and applying patches to affected customers, and urged customers that had not yet completed the update to apply the security patch as soon as possible.

    Financial regulators also recommended sharing DaouOffice-related security measures and applying the emergency patch. According to Boannews’ incident analysis and KISA’s patch advisory, customers using DaouOffice version 3.6.8.5 or earlier are included in the scope of the measures.

    Source material

    This article was prepared by reviewing the following original source: Boannews: Bithumb and Hanyang Securities hacked in zero-day attack against DaouOffice due to insufficient access control

  • Anthropic’s FlashProve Verifies AI Model Output Origins

    Anthropic’s FlashProve Verifies AI Model Output Origins

    Anthropic is researching FlashProve, an open source system that cryptographically verifies the origin of outputs generated by AI models. The system aims to prove, through “provable inference,” that a specific output was generated by a designated model, and has been presented as a new approach to AI model verification. Published technical specifications and some working code are available, but FlashProve remains at an early research stage, with no plans to release it through Anthropic or another research institution.

    How FlashProve detects outputs disguised as those from another model

    FlashProve is designed to let recipients confirm whether a message actually came from its sender, much like cryptographic email signatures. It is intended to withstand attempts to pass off one model as another and to verify claims that an AI company has substituted a less expensive model to reduce costs or used a more expensive model to inflate performance claims.

    The researchers considered cases in which a developer claims that a state-of-the-art cybersecurity model checked a software library for vulnerabilities, or a company claims that an appropriate model reviewed its business plan. FlashProve was proposed as a way to verify which model is actually associated with such claims.

    For this purpose, an AI research lab would need to publish a “fingerprint” for each model it releases, link that fingerprint to specific outputs and verify the link cryptographically. Just as an email signature identifies the sender of a message, a model fingerprint provides information that identifies the origin of an output. TechCrunch’s report on FlashProve describes the system as a research project focused on verifying model identity.

    Verifying closed models without revealing their weights

    A model fingerprint does not expose the model’s internal weights. Weights are the internal numerical values that define how a model operates, and companies that operate closed models generally keep them secret. A research lab could therefore publish a fingerprint without giving up its most important asset, and FlashProve could potentially be applied to commercial models as well.

    The verification process is also designed to be lightweight. FlashProve is intended to run verification on a local device, allowing users to check the origin of an output without relying on a separate centralized service. However, it has not been confirmed whether the system works with every closed model in a real service environment, and the current release consists of interim research results.

    Potential practical uses and remaining challenges

    FlashProve could be used to verify claims that a third party used an advanced model for a specific task or to check the results of software security reviews. However, the system remains a research result with published technical specifications and working code for several components, and no deployment schedule has been announced.

    The researchers described the release as an intermediate research step intended to share the work so that other researchers can build on the existing results. FlashProve’s technical specifications and some working code have been released under an open source license, with no plans for a future release.

    Source

    This article was written using the following source: TechCrunch — Anthropic is working on a system to prove AI models’ identity

  • GitHub Trending 2026-11-04: Three AI Agent Integration Tools

    GitHub Trending 2026-11-04: Three AI Agent Integration Tools

    In the GitHub Trending daily rankings collected on November 4, 2026, vercel-labs/agent-desktop, D4Vinci/Scrapling, and mattpocock/skills led in star growth. The three repositories occupy different domains. Each handles a distinct execution layer—desktop control, web data collection, and reusable development procedures—while sharing a common approach to connecting AI agents with real work environments.

    agent-desktop: Controlling Desktop Apps Through Accessibility Trees

    vercel-labs/agent-desktop is a computer use CLI that lets AI agents observe and control desktop applications by reading operating system accessibility trees rather than relying on screenshots or pixel matching. It supports macOS, Windows, and Linux, returns accessibility trees in JSON, and assigns a ref to each interactive element. Agents can use these refs to click or enter input, then read the UI again to verify the result and proceed to the next task. The iterative control loop is built into the agent, while the repository does not include a model.

    This structure distinguishes the tool from pixel-based approaches that depend on button locations or screen resolution because it operates on structured elements. The project is available as both a CLI and a C library. It is well suited to environments that require genuine on-screen interaction, such as desktop automation and GUI application testing. However, snapshots, clipboard data, command output, and debugging materials may contain sensitive desktop content, so they should be kept separate from public logs or uploads.

    As of November 4, 2026, the repository gained 2,463 stars that day and had accumulated 13,972 stars in total. Its primary development language is Rust, and it is released under the Apache-2.0 license.

    Scrapling: From Individual Requests to Large-Scale Crawling

    D4Vinci/Scrapling is a Python web scraping framework that handles everything from individual requests to large-scale crawling. It combines fast HTTP requests, stealth browsing, parsing, and concurrent crawling in a single library. It supports static page collection, JavaScript rendering, website interaction, and data extraction from API calls made within pages. It can be used from the terminal and by AI agents through its CLI, MCP server, and Agent Skill interface.

    • It provides fetching and interaction features, including Cloudflare Turnstile and interstitial handling, persistent sessions, and background API capture.
    • It supports CSS, XPath, text, and regex searches, adaptive element tracking, matching similar elements, and clean Markdown output.
    • It offers concurrent spiders, proxy rotation, automatic retries, AutoThrottle, pause and resume functionality, and streaming.
    • Collected results can be exported as JSON, JSONL, CSV, or XML.

    It covers a broad range of web data collection workflows, from research that extracts only a few fields to tasks that capture an entire site in Markdown. As of November 4, 2026, it had gained 2,006 stars that day and accumulated 95,705 stars in total. Its primary language is Python, and it uses the BSD-3-Clause license.

    skills: Collecting Small, Composable Development Procedures

    mattpocock/skills collects agent skills used in real application development and is designed to be adapted and combined for individual projects. Rather than taking over the entire development process like GSD, BMAD, or Spec-Kit, it focuses on small, adaptable, individual skills. It emphasizes that the skills can be used with any model and are structured around engineering experience.

    Installation methods vary depending on the agent in use. The Claude Code plugin updates itself by default, Codex updates when it starts, and Gemini CLI is refreshed by running the command again. With the skills.sh method, editable files are copied into the project and updated manually by the user. Only one method should be selected for a given agent to prevent installed skills from being duplicated.

    It can be used to standardize repetitive development tasks or turn them into project-specific instructions. As of November 4, 2026, the repository gained 1,376 stars that day and reached 312,115 stars in total. Its primary language is Shell, and it uses the MIT license.

    Comparing the Execution Layers of the Three Repositories

    The differences among the three projects are most apparent in their connection points rather than their number of features. agent-desktop reads the application structure exposed by the operating system, Scrapling collects web information through networks and browsers, and skills organizes actions developers want to repeat into file-based skills. In environments that require both desktop control and web collection, a natural approach is to combine an execution tool that does not include its own model with an interface for agents. Conversely, when consistency in application development is more important, model-independent, composable skills can provide the starting point.

    Repository Primary Language Stars Gained Today Total Stars Primary Use
    vercel-labs/agent-desktop Rust 2,463 13,972 Control desktop apps through accessibility trees and refs
    D4Vinci/Scrapling Python 2,006 95,705 Handle everything from HTTP requests through concurrent crawling and data export
    mattpocock/skills Shell 1,376 312,115 Provide adaptable and composable development agent skills

    Source

    This article was prepared by consulting the following source: GitHub Trending — GitHub Trending 2026-11-04: agent-desktop, Scrapling, skills

    Cross-checked sources:

  • Changed an Object ID? Why That Alone Is Not IDOR Evidence

    Changed an Object ID? Why That Alone Is Not IDOR Evidence

    The most common mistake during a security assessment is to label an issue as IDOR solely because changing an object ID in a URL produced a different response. If a search returns another profile or the response format changes, the observation belongs in the tester’s notebook, but it is not enough evidence on its own to support a vulnerability report. The actual question is not whether an identifier can be manipulated, but whether an unauthorized actor was able to read or modify a resource that the access policy should have denied them.

    This distinction is central to the IDOR determination criteria. As in the original example, changing 1001 to 1002 in GET /api/account/1001/profile and receiving a response does not prove IDOR. The questions that must be answered are whether the target resource actually belongs to another user, whether the server checks the current requester’s access permissions, and whether an unauthorized user can view or modify that resource. Ultimately, the starting point for the determination is whether the behavior violates the application’s intended access-control policy.

    Why a Single Response Code Is Not Enough

    A status code shows the result of a control, but it does not describe the full scope of a vulnerability. If a successful response contains data that was intentionally public, such as a public profile, there may be no issue. Conversely, even if one path denies access, the same resource may still be readable or modifiable through another API representation or separate feature, and that path must be tested independently.

    A common structural mistake is to treat reads and modifications as a single category. Retrieving a profile is a comparatively passive information disclosure, while modifying an order or deleting a file involves a state change and a different potential impact. Therefore, when applying the IDOR determination criteria, record successful reads, modifications, and deletions separately, and explain how each result deviates from the expected permission policy.

    Preparation: Document the Test Relationships First

    Before testing begins, the test accounts, ownership relationships, and access policies must be clearly defined. Prepare test resources owned by separate accounts and document each account’s role and permitted access scope. Do not modify real user data or production data, and perform all requests only within the formally authorized scope or a practice environment. Learning resources on this topic are available in PortSwigger’s Access Control vulnerabilities and Insecure Direct Object References documentation.

    The discussion covering the original question can also serve as practical reference material for the core principles of IDOR diagnosis. The source also recommends working only in an authorized lab or an explicitly permitted bug-bounty scope when practicing access control and IDOR techniques.

    Step-by-Step Verification Workflow

    The first step is to capture the owner’s legitimate request. In the browser’s developer tools, use the Network panel to determine whether the object identifier is carried in the URL, query string, JSON body, or headers. The second step is to change only the identifier while preserving the authenticated session and requester. At this stage, compare the status codes, body fields, and error messages from the legitimate and modified requests side by side.

    The third step is to verify the ownership relationship of the target resource. First establish whether the modified identifier points to another account’s nonpublic resource. Even if the returned values differ, they cannot be elevated to IDOR evidence if the data was intended to be public. The fourth step is to examine whether the server handles authentication and authorization separately. Checking whether a user is logged in is an authentication check, while comparing the authenticated principal with the resource owner or an authorized permission relationship is an authorization check. IDOR is more likely to occur when resource-level authorization checks are missing or applied inconsistently across API paths.

    ※ Note: The following configuration and code are conceptual simulation examples (Illustrative Example, not official spec) provided to aid understanding.

    # Save the owner’s request and the unauthorized request with only the identifier changed.
    curl -sS -H 'Authorization: Bearer TEST_TOKEN' \
     'https://authorized.example/api/account/OWNED_ID/profile' > owner.json
    
    curl -sS -H 'Authorization: Bearer TEST_TOKEN' \
     'https://authorized.example/api/account/OTHER_ID/profile' > candidate.json
    
    # Compare the status code, presence of sensitive fields, and results of any changes.
    jq -S 'keys' owner.json
    jq -S 'keys' candidate.json

    These commands are a conceptual example of the comparison workflow. Actual assessments must use only approved hosts and test resources. Do not compare returned fields alone; confirm whether nonpublic information was actually exposed. Test modification methods separately as well, and limit them strictly to test data. Record read tests and modification tests as distinct results.

    Test Other Paths and Authorization Routes Together

    An assessment should not end with a single URL substitution test. Check alternate access representations for the same resource, including other API paths, Graph APIs, batch operations, file downloads, and administrative features. For each path, map the authenticated principal, target resource, and permitted roles again. Also determine whether access-denied responses reveal the existence or attributes of sensitive resources.

    The report should include the original request, the request with only the identifier modified, the account used, the owner account, the expected policy, the actual responses, whether nonpublic data was exposed, and whether any changes occurred. Do not conclude that the implementation is secure merely because the server denied access; confirm that behavior across other access paths is consistent. Likewise, do not declare a vulnerability solely because a successful response was returned.

    Reproducible Records Define the Quality of a Vulnerability

    A high-quality IDOR report demonstrates a clear access-control failure rather than an attacker’s creativity. Document separately that an identifier could be changed, that a different response was returned, and that nonpublic data inaccessible under the policy was viewed or a resource was modified. Without the third piece of evidence, the finding should remain a suspected issue that does not meet the IDOR determination criteria.

    The same principle is necessary from an access-control design perspective. For every resource request, the server should verify the authenticated principal’s ownership or authorized permission relationship and should not trust owner identifiers supplied by the client. This standard not only ensures that the current request is validated, but also requires the same resource-level access controls to be applied across other API representations and administrative paths.

    Try This Now

    • Prepare two authorized test accounts and a test resource owned by each account, then document the ownership relationships.
    • Capture one legitimate request and record where the object identifier is transmitted and which principal is authenticated.
    • Keep the session intact, change only the identifier, and compare the response bodies and returned fields.
    • Test read and modification methods separately and record the results of changes to test data.
    • Organize the original request, modified request, expected policy, and actual evidence of exposure or change into a report.

    Original Source

    This article was prepared after reviewing the following original source: r/AskNetsec — Is changing an object ID enough to identify an IDOR vulnerability?