A newly described flaw in the developer editor underscores a simple but dangerous reality: in modern software workspaces, one user interaction can become a credential incident.
Kali365 appears to be expanding a phishing playbook built around identity workflows, showing how token theft and login abuse can travel across very different services.
Kali365 is reported to have widened its targeting from Microsoft 365 token theft to Okta SSO and MAX Messenger, a sign that commoditized phishing is shifting toward reusable session abuse.
A disclosed attack chain involving VS Code and GitHub.dev shows how a single click can become a credential problem, not just a nuisance.
A reported browser-editor flaw shows how a single UI mistake can turn a trusted code workspace into a path toward OAuth token theft and private-repo access.
A reported zero-day in Visual Studio Code puts a familiar workflow under a harsher light: one link click, one credential class, and a potentially wide blast radius depending on token scope.
A reported weakness in Visual Studio Code’s webview layer raises a familiar but dangerous question: what happens when an editor boundary and a GitHub authorization token sit too close together?
CVE-2026-4387 shows how a workstation-side leak in a privileged access client can turn reusable login state into a potential path toward infrastructure access.
A seemingly useful npm package for OpenAI Codex became a supply-chain trap, showing how developer convenience can double as credential exposure.
A malicious Codex UI package in npm was reported to have stolen OpenAI refresh tokens, a reminder that developer tooling can turn into a credential-harvesting channel with account-takeover consequences.
Tycoon 2FA is a reminder that identity attacks do not need to break passwords if they can relay a live login and harvest the session behind it.
A phishing service built around OAuth device code flow shows how attackers can turn a legitimate sign-in path into token theft, session hijacking, and MFA bypass.
A phishing-as-a-service platform is turning Microsoft’s device-code sign-in into a turnkey path for token theft, session hijacking, and quieter cloud compromise.
A phishing kit linked to Telegram distribution is pushing attackers toward session theft, turning a successful sign-in into a longer-lived foothold inside cloud accounts.
A reported phishing service named Kali365 points to a harder problem than stolen passwords: cloud identity abuse that can ride on legitimate OAuth and device-code sign-in paths.
A Node.js remote-access trojan is being examined as a real-time secret harvester, a reminder that one infected workstation can put source control, cloud access, and automation accounts at risk.
A typosquatting wave in the npm ecosystem is a reminder that one routine install can become a high-value secret hunt.
Attackers are abusing a real OAuth sign-in path to turn user cooperation into token theft, shifting the fight from passwords to the identity layer itself.
A phishing campaign tied to the EvilTokens kit is described as using Outlook invites and device-code login abuse to target Microsoft 365 sessions rather than passwords.
Attackers are abusing a standard cross-device sign-in path to steal Microsoft 365 tokens, sidestep ordinary MFA expectations, and turn a trusted identity workflow into a foothold for mailbox abuse.