SShortSingh.
Back to feed

Token-spraying campaign replays stolen Microsoft 365 sessions to bypass MFA and passwords

0
·1 views

Security firm Huntress reported on October 22, 2026 a campaign in which attackers stole session tokens after victims completed a legitimate login and MFA challenge. The attackers then replayed these tokens from their own machines against Microsoft 365, so the stolen sessions did not require passwords or fresh MFA. Roughly 200,000 sign-in attempts were made, and 497 of them succeeded. The activity leaves few of the usual warning signs, such as phishing pages or suspicious geographic sign-ins. Huntress recommended checking identity logs for three signals that do not require access to token values.

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 ·

Reviving an Abandoned Fastify Plugin for RFC 9457 Problem Details

A developer revisited a Fastify plugin, fastify-rfc9457, that they had published and then left untouched for about a year. Its existing tests still passed, but the lint script had never worked and its dependency had moved to a new major version, so they updated it and released version 1.0.1 through a more secure GitHub Actions publishing flow. The plugin addresses the common problem of APIs returning inconsistent error formats, which forces clients to write custom parsers. It implements RFC 9457, the IETF standard for HTTP error responses that defines a consistent shape using the application/problem+json content type. The plugin applies this format automatically across routes, including validation failures and not-found errors, so developers don't have to format every error by hand.}

0
ProgrammingDEV Community ·

Governance Gaps: Actions Outside the Tool Registry and Who Owns Them

A events table received rows from two paths: an AI assistant calling a registered tool, and a plain HTTP endpoint that bypasses the tool registry and the AI side-effect ledger. The author argues that governance should be judged by which execution paths were verified, not by how many tools are registered. The runtime registers 61 tools, but external MCP tools appear in a separate admin catalogue requiring higher permissions, leaving auditors with an incomplete view. The gate treats unregistered tools as a matter for the executor, so passing the gate does not confirm registration. The author also cites an earlier mistake in which a hand-maintained metadata table drifted from the live tool set, and recommends checking the registry against actual entry points.

0
ProgrammingDEV Community ·

Developer Runs Personal AI Agent on Home NAS Instead of Cloud

A developer built a personal AI agent that runs in a container on a home UGREEN DXP2800 NAS rather than a cloud service. The agent's identity is defined by plain-text files covering its conduct rules, personality, the owner's profile, and daily notes, which it reads before responding. Each Monday it pulls tasks from Notion, generates an HTML recap, and emails it, with safeguards against duplicate sends. The agent also wrote and deployed a public static demo page, agent-mailbox, that shows only fictional data, while real data stays on the home machine. The project was submitted to a Hacktoberfest open-source AI challenge.

0
ProgrammingDEV Community ·

Developers Weigh New AI Code Editors as Coding Agents Reshape Workflows

The article surveys roughly ten standalone AI code editors and many AI coding tools, including Cursor, now owned by SpaceX, Google Antigravity, Amazon Kiro, Trae, and Zed. It notes that Coinbase's AI acceleration lead told engineers in January 2026 to stop using their IDEs and rely on coding agents for all work. Anthropic data reportedly shows Claude Code sessions roughly doubling in length over three months. The piece argues companies may begin treating AI token usage as a managed resource, with budgets and dashboards, under a concept it calls "Claudeonomics." It concludes that developers who deliver the most output per token will stand out most.