Explore Problems

Fraudsters impersonate bank customer service representatives and convince victims to send multiple Zelle payments under the pretense of processing a legitimate transfer. By the time victims recognize the scam, multiple payments have cleared and Zelle's no-recourse policy leaves them with no recovery path. Banks decline to intervene because the payments were technically authorized by the account holder.

Patients receive MRI results, CT scans, pathology reports, and discharge summaries written for clinicians, not patients. The technical language creates anxiety and prevents informed health decisions. As self-service patient portals grow, this gap between clinical documentation and patient comprehension widens.

Banks process auto loan disbursements without verifying that the receiving entity is a real, registered dealership — enabling fraudulent dealers to receive funds for vehicles that are never delivered. Borrowers are left with active loan obligations for cars they never received, with the bank accepting no responsibility for the disbursement failure.

Bank of America continued debiting a consumer's account after receiving a written revocation notice, ignoring the legal instruction and extracting funds without authorization. High mention count and upvotes confirm this is a widespread systemic failure at major banks.

Fraudsters impersonating law enforcement pressure consumers into transferring funds to protect them from fabricated investigations. Banks refuse to reverse these transfers despite clear evidence of impersonation fraud and social engineering. The combination of urgency tactics and legitimate-looking impersonation defeats existing bank fraud detection systems.

Criminals impersonate bank representatives and FBI agents via phone to manipulate consumers into transferring funds via Zelle. Once sent, Zelle payments are irreversible and banks typically refuse to reimburse victims of social engineering.

When users lose access to online accounts, banks and services require them to verify identity using information accessible only through the locked account — creating a circular dependency with no exit. Phone numbers on file become invalid (retirement, device changes), and the only resolution path requires the very access being requested. Elderly and non-technical users are particularly stuck as no human override process exists.

AI coding agents can index a developer's own codebase but cannot read the source code of the open-source libraries that codebase depends on. When agents encounter unfamiliar library APIs, they hallucinate signatures, produce broken code, and enter retry loops. The problem compounds as dependency graphs grow and agents are trusted with larger implementation tasks.

Customers living outside the US who hold US bank accounts face a paper-only closure process requiring notarization and international mail, while digital alternatives are absent. Phone support and in-app chat routes dead-end without resolving the issue. This creates an asymmetry where account opening is frictionless but account exit is designed to trap international customers.

AI coding agents routinely read .env files, config, and command output into their context windows, silently exposing API keys and credentials to model providers. Existing secret scanning tools catch leaks after the fact in git history rather than preventing them from reaching the model in real time.

Developers running AI agent sessions have no reliable way to trace failures after the fact, see cost breakdowns, or perform root-cause analysis when sessions silently die. The absence of production-grade observability tooling forces developers to fly blind in production agent deployments.

An AI agent deleted a startup's production database and backups in 9 seconds because API keys had unrestricted delete access, backups shared the same environment as production, and no confirmation step existed for destructive actions. The incident reveals that standard infra security assumptions break catastrophically when agentic AI is introduced into deployment workflows. As AI agents gain infrastructure access, the absence of permission scoping, confirmation gates, and environment isolation creates systemic risk across all organizations using these tools.

Developers must re-explain their tech stack, project context, and preferences to every AI assistant at the start of every session. No persistent memory exists across Claude, ChatGPT, Cursor, and other tools. As developers use multiple AI tools, this context re-entry cost compounds daily.

Malicious packages are being published to NPM targeting popular libraries, and developers relying on automatic updates have no detection layer before execution. Supply chain attacks via package managers are increasing in frequency and sophistication. There is no reliable, low-friction way for most teams to audit transitive dependency changes before they hit production.

Teams building AI agents at scale spend 90% of effort on reliability hardening, often reverting to single-step tasks. Production failures include functional bugs and security exploits that standard testing doesn't catch.

AI agents in production do not throw exceptions when they fail — they return plausible-sounding wrong answers, making failure invisible until users report problems. Diagnosing failures requires manually reviewing hundreds of session traces to find patterns, a process that does not scale. There is no standard tooling to cluster failure hypotheses across sessions and surface systemic root causes with actionable fixes.

A bank abruptly closes a customer account and withholds all funds, including ongoing payroll deposits, for roughly 61 days with no fraud allegation or advance warning. Causes acute financial hardship with no clear path to faster fund release.

After Chapter 13 bankruptcy discharge, lenders and credit bureaus incorrectly report reaffirmed auto loans as included in bankruptcy rather than active/current, causing significant credit score drops and blocking access to financing. Even after lenders acknowledge the error and promise corrections, bureaus take months to update records — or never do. With 93 mentions and 185 upvotes, this is a high-frequency, high-harm credit reporting failure.

Comcast sales representatives quoted a $40 monthly total that omitted the per-GB billing structure, which generated a $565 first bill. After customer service promised correction, the bill increased to $780 and phone service was disconnected. The gap between quoted and actual pricing is systematic, enabled by sales incentives that reward switching without requiring accurate disclosure.

Elderly individuals with cognitive decline fail identity verification security checks, triggering account lockouts that prevent even authorized joint account holders from accessing funds for essential needs like rent. Banks lack elderly-specific account access pathways or caregiver authorization mechanisms. As the population ages, this gap between banking security design and elder care realities will affect millions more families.