Urgent.News

What's breaking now, across thousands of outlets.

Tech

OAuth Consent Phishing: The Attack a Password Change Does Not Fix

The FBI's Internet Crime Complaint Center published PSA I-090126 on September 1, 2026, and it describes an attack that quietly defeats the two things most people rely on: changing your password, and having multi-factor authentication turned on. Neither one helps here. That is not a flaw in either — it is that this attack never touches your password at all. What consent phishing actually is You…

The FBI's Internet Crime Complaint Center has issued a warning about a phishing attack that can bypass password changes and multi-factor authentication. This attack doesn't manipulate passwords or MFA, but instead targets a less-protected OAuth consent process. Users often unknowingly grant permission to apps during the OAuth flow, which allows the app to access their data without needing their password.

The FBI explains that the damage done by this attack can only be undone by removing the consent grant from the app's connected applications settings, rather than changing the password or verifying MFA. The attack is typically launched through fake messages from impersonating individuals like government officials or event coordinators, asking the user to review documents or confirm attendance.

The attack is especially dangerous because the compromised OAuth token can remain valid for months, granting the attacker ongoing access to the user's data. The warning emphasizes the importance of regularly auditing granted permissions and revoking access to apps that are no longer needed or trusted. This process involves checking connected applications lists on platforms like Google, Microsoft, LinkedIn, GitHub, Dropbox, Slack, Zoom, and Meta, and revoking permissions for any unused or suspicious apps.

The FBI advises users to revoke the grant immediately, change their password afterward, and then review any suspicious login activity or forwarded emails. The warning concludes by urging users to periodically review their OAuth consent settings, as a simple two-minute audit can significantly reduce the risk of this type of attack.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

issued.live is live

issued.live is open to the public today. This note is about how it is built and why it behaves the way it does, because those choices are the difference between a lookup you can rely on and one that…

  • issued.live launched today for real-time domain data access
  • Index holds 334 million domains with 15.9M certificates ingested
  • Data updates continuously, served in JSON, Markdown, and MCP

issued.live: Certificate Transparency, ICANN Registrations and DNS in One API

Every certificate issued for every domain on the public internet gets written to a public log. Anyone can read them. Almost nobody does — because the raw feed is a firehose of tens of thousands of…

  • Certificate Transparency logs record every public domain certificate continuously.
  • issued.live aggregates data from CT logs, ICANN registrations, and DNS scans.
  • The service offers JSON, Markdown, and MCP formats for domain lookup information.

I sell social media automation. My survey says people want the opposite.

I work at Publora — an API and MCP for publishing to social networks from one place, including through an AI agent. So, in a sense, my job is selling automation for posting.

  • Survey reveals people want control over final posting step in social media automation
  • AI use limited to ideation or time constraints, not for publishing
  • Human involvement valued for security, personal touch, and content approval

Moving image work into the browser took that bill to zero

For about two months last year I had a habit: check the API usage graph before anything else in the morning. Not because traffic was flattering — because every time that line went up I had to work out…

  • Moved image processing to users' browsers to eliminate API costs
  • Services like background removal, AI upscaling, and PDF processing ran locally
  • Site became free, unmetered, but limited by free service constraints

Hitting an image size ceiling with Rust and WebAssembly

Many image tools expose a quality slider. Forms and government portals usually expose a different requirement: “the file must be under 100 KB.” Those are not the same problem.

  • Implement HEIC converter in browser using Rust compiled to WebAssembly
  • Outputbytes = targetkb 1024 invariant for image size control
  • Separate conversion path from compression for clean implementation

More from Thursday 3 September →