Study of 170M Residential Proxy IPs Exposes Rapid Churn Undermining Fraud Detection

·1 views

A 90-day analysis by IPinfo covering over 170 million residential proxy IP addresses, conducted between October and December 2025, found that this infrastructure changes far faster than most fraud detection systems assume. Residential proxy IPs were active for an average of just 4.56 days, with IPv6 addresses lasting only 1.29 days on average, and 60% of all observed IPs appearing only once. Around 78% of IPs vanished within 30 days of first being detected, making historical reputation data largely unreliable by the time it becomes actionable. The study also found that the same underlying IP infrastructure is frequently shared across multiple proxy providers simultaneously, further complicating provider-level identification. Together, rapid infrastructure turnover and cross-provider overlap pose a significant challenge to reputation-based and risk-scoring systems used in abuse and fraud detection.

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)

How One Developer's Work Journal Quietly Transformed Under AI-Assisted Coding

A software developer who has maintained a Notion work journal since July 2021 noticed it had fundamentally changed over the first half of 2025. What began as a few daily lines for self-reviews and 1-on-1 meeting prep gradually gave way to pasted AI session transcripts and incomplete 'breadcrumb' notes pointing to where context actually lived. The shift happened without any conscious decision, driven by denser workdays, faster context-switching, and AI coding sessions that generated far more output than traditional meetings. Reading back six months of entries — February through July — the developer found three distinct note-taking styles had emerged, only one of which was deliberately chosen. The journal effectively documented its own transformation from personal reflection tool to a navigation system for AI-generated context.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Durable Approval Tokens Are Unsafe Unless Bound to Exact Approved Parameters

A software engineering discussion highlights a critical flaw in human-in-the-loop AI agent approval systems: persisting an approval token does not guarantee it reflects what the human actually reviewed. Between the moment a user approves an action and the moment it executes, underlying details such as file contents, symlinks, or recipient lists can silently change. This mirrors the classic time-of-check to time-of-use (TOCTOU) race condition, but stretched across minutes or hours due to human response time and process restarts. The proposed fix is to bind each approval to a cryptographic fingerprint of the exact parameters rendered to the user, then recompute and verify that fingerprint at execution time, failing closed on any mismatch. Aggressive expiry of approval tokens is also recommended, as it limits how stale a decision can become before it is acted upon.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

OpenAI Flags Astra as First Model at Critical Cybersecurity Risk Threshold

OpenAI has designated its upcoming Astra model as its first critical cybersecurity model under its internal Preparedness Framework, placing it at the highest cyber-risk tier. The classification means OpenAI is implementing additional controls over Astra's development, following internal evaluations that raised concerns about its cyber capabilities. The company reportedly paused certain activities related to Astra while stronger safeguards were put in place. Rather than a standard product launch, the move reflects a governance decision requiring heightened testing and deployment discipline before broader access is granted. For enterprise customers, the designation signals that advanced AI cyber capabilities may face tighter access restrictions and oversight requirements going forward.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Why SOLID Principles Alone Are Not Enough for Complex Software Design

A DEV Community article series on Low-Level Design argues that while SOLID principles help engineers build well-structured individual classes, they do not address how those classes collaborate at scale. As software systems grow, new design challenges emerge around object creation, algorithm selection, inter-component communication, and extensibility. The author uses a city-planning analogy to illustrate that designing good individual buildings does not automatically produce a functional city — the connections between them matter equally. Design Patterns, the article contends, exist specifically to solve these structural and collaborative problems that SOLID leaves unanswered. The piece serves as an introduction to a mini-series that will explore why Design Patterns were created and how they complement object-oriented principles.

0 comments Read more at DEV Community