#session-hijacking — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #session-hijacking, aggregated by home.social.
-
phpBB Flaw Enables Instant Account Takeover
A single HTTP request can give an attacker instant access to any user's account, including administrator accounts, without needing a password - a vulnerability rated 9.4 on the CVSS scale that's affecting phpBB versions up to 3.3.16 and 4.0.0 alpha.
#AuthenticationBypass #Phpbb #Ptt2026004 #Cve2026xxxx #SessionHijacking
-
Hook, Line, and Sinker: Why People Still Fall for “Official” Emails
3,206 words, 17 minutes read time.
The digital landscape is a cold, relentless stretch of asphalt where the rain never stops and the shadows are always reaching for your throat. It is an environment built on the fundamental architecture of trust, yet it is that very trust that serves as the primary vector for the modern grift. When we look at the evolution of the phishing landscape, we aren’t just looking at a series of technical failures or a lack of robust filtering; we are looking at the exploitation of the human operating system. Most analysts want to talk about SPF, DKIM, and DMARC as if they are the ultimate shields against the storm, but they often ignore the fact that the most sophisticated code in the world cannot patch a moment of panic. The “Official” email is the modern equivalent of a knock at the door at three in the morning; it carries an inherent authority that bypasses the logical gates of the brain and targets the raw, unrefined nerves of social obligation and fear of consequence.
Analyzing the recent waves of business email compromise and high-stakes credential harvesting, I see a clear pattern that suggests we are losing the war of attrition because we refuse to acknowledge the psychological heavy lifting being done by the adversary. The craft has moved far beyond the broken syntax and desperate pleas of a decade ago, evolving into a surgical instrument that mirrors the exact cadence of corporate bureaucracy. These attackers are not just hackers anymore; they are student of institutional behavior who understand that a well-placed “Urgent Action Required” notice from a spoofed human resources alias is more effective than any brute-force attack. By the time the target realizes the landing page is a mirror of a Microsoft 365 login, the credentials have already been spirited away into a database in a jurisdiction where the law doesn’t have a name.
The Psychological Mechanics of the Digital Ambush
The success of a phishing campaign relies on the deliberate manipulation of cognitive load and the exploitation of ingrained social hierarchies. When an individual receives an email that appears to originate from a high-level executive or a government entity like the Internal Revenue Service, the brain undergoes a shift from analytical processing to a reactive survival mode. This is not a matter of intelligence or technical savvy, as even seasoned administrators have been known to trip over a well-constructed lure when the timing is right. The adversary waits for the moment of highest friction—the end of a quarter, the middle of a migration, or the chaos of a public holiday—to drop a message that demands immediate attention. This creates a sense of urgency that effectively narrows the victim’s field of vision, making them ignore the subtle discrepancies in the sender’s address or the slightly off-kilter phrasing of the call to action.
Furthermore, the concept of social proof is weaponized within these emails to provide a false sense of security that lulls the victim into a state of compliance. Many of these “official” messages are designed to look like a small part of a larger, ongoing process, such as a mandatory security update or a routine document review. By framing the malicious link as a necessary step in a boring, everyday task, the attacker sidesteps the natural skepticism that usually accompanies an unexpected request. Consequently, the victim views the interaction not as a potential threat, but as a minor hurdle to be cleared so they can return to their actual work. This mundane nature of the attack is its greatest strength, allowing it to slip through the cracks of human intuition while the technical defenses are busy looking for more overt signs of intrusion.
Why Technical Defense Perimeters Often Fail the Human Test
We have spent billions of dollars on secure email gateways and advanced threat protection, yet the “official” email remains the most successful entry point for ransomware and data exfiltration. This failure is rooted in the inherent tension between usability and security, where the need for seamless communication often creates gaps that an attacker can drive a truck through. A secure email gateway is essentially a filter designed to catch known bad patterns, but the modern phisher is an expert at staying just beneath the threshold of detection. They use legitimate infrastructure, such as compromised Small Business Server accounts or reputable cloud hosting providers, to launch their campaigns. When a malicious email originates from a trusted IP address with valid cryptographic signatures, the technical gates swing wide open, leaving only the human at the keyboard to make the final call.
In addition to the subversion of trust, the rapid pace of digital transformation has outstripped the ability of the average user to verify the authenticity of their communications. As organizations move their operations to various third-party SaaS platforms, the number of “official” domains that a user interacts with on a daily basis has skyrocketed. It is no longer enough to look for a single corporate domain; employees are now expected to recognize notifications from payroll systems, project management tools, and cloud storage providers, all of which use different naming conventions and email templates. This fragmentation creates a smokescreen for the attacker, who can easily hide a malicious domain amidst the noise of a dozen legitimate ones. As a result, the mental fatigue of constantly verifying these sources leads to a state of “security nihilism,” where the user eventually stops checking altogether and simply clicks through to stay productive.
The anatomy of a modern credential harvest is a masterclass in deceptive minimalism, designed to exploit the very tools we use to stay organized and secure. Looking at the mechanics of the “Official” document lure, I see a devastatingly effective strategy that leverages the ubiquity of shared drives and collaborative platforms like SharePoint or DocuSign. The attacker doesn’t need to attach a piece of malware that might trigger an endpoint detection system; they simply provide a link to a legitimate-looking landing page that asks for a login to “view the protected file.” This transition from a trusted email environment to a browser-based authentication prompt is where the logic breaks down for most users. Because the initial email looked like a standard notification—complete with the correct legal disclaimers and corporate branding—the user’s brain has already cleared the transaction for takeoff. By the time they land on the spoofed login page, they aren’t looking for a scam; they are looking for their document, and they will hand over their credentials to get it.
The danger is compounded by the rise of “Living off the Land” techniques in the phishing world, where attackers use the victim’s own tools against them. When an adversary compromises a legitimate account within a supply chain, they can send “official” emails from a truly valid source to that person’s entire contact list. This lateral movement within a trusted ecosystem is the nightmare scenario for any security operations center because the traditional red flags simply do not exist. There is no mismatched “From” header to inspect, and the link often points to a real file hosted on a real corporate server that happens to contain a malicious redirect. In this context, the victim isn’t falling for a fake; they are being misled by a compromised reality. This level of deception makes it nearly impossible for the average employee to distinguish between a routine request and a high-stakes heist, especially when the message arrives in the middle of a high-pressure workday.
The Institutional Cost of Authority-Based Exploitation
When we break down the damage, we see that the financial toll of these “official” phishes is often eclipsed by the erosion of internal culture and institutional trust. Every time a successful campaign rips through a department, the aftermath involves a heavy-handed response from IT that usually includes more restrictive policies and mandatory, often condescending, training modules. This creates a friction-filled environment where employees start to view their own security team as an adversary or a hurdle to their productivity. Furthermore, the psychological impact on the individual who clicked the link can be profound, leading to a loss of confidence that hampers their work performance and makes them less likely to report future suspicious activity for fear of further embarrassment. Consequently, the organization becomes more brittle, hiding its vulnerabilities behind a facade of compliance while the actual risk remains unaddressed and festering in the shadows.
Looking at the broader economic landscape, the industrialization of phishing kits has lowered the barrier to entry for low-level criminals, allowing them to masquerade as sophisticated entities with the click of a button. These kits come pre-loaded with high-fidelity templates for every major bank, government agency, and tech giant, ensuring that even a novice operator can launch an “official” campaign that looks professional. This democratization of high-end social engineering means that the volume of attacks is constantly increasing, creating a background radiation of fraud that everyone must navigate daily. The sheer frequency of these encounters leads to a desensitization of the workforce, where the warning signs that used to trigger an alarm are now ignored as part of the digital noise. This saturation of the communication channel is exactly what the adversary wants, as it ensures that eventually, someone, somewhere, will be tired or distracted enough to swallow the hook.
The Illusion of Multi-Factor Authentication as a Total Shield
One of the most dangerous myths in the current security climate is the idea that Multi-Factor Authentication is an unhackable barrier that renders phishing obsolete. While MFA is a critical layer of defense, the “official” email has evolved to bypass it through sophisticated techniques like adversary-in-the-middle attacks and session hijacking. In a standard MFA-bypass scenario, the malicious email leads the victim to a proxy server that mimics the real login page in real-time. As the victim enters their username, password, and the subsequent one-time code from their phone, the attacker’s server passes those credentials to the actual service and steals the resulting session cookie. To the user, the experience is seamless and appears entirely “official,” but behind the scenes, the attacker now has a persistent foothold that bypasses the need for a password entirely. This proves that even our most robust technical solutions can be undermined by a well-executed social engineering play that targets the moment of authentication.
Moreover, the phenomenon of “MFA Fatigue” has become a potent weapon in the attacker’s arsenal, turning a security feature into a vulnerability. After sending a series of “official” emails claiming there is a problem with an account, the attacker will trigger a barrage of push notifications to the victim’s mobile device. The goal is to wear the person down until they hit “Approve” just to make the buzzing stop, assuming it’s a glitch in the “official” system. This exploit doesn’t require technical brilliance; it requires an understanding of human frustration and the tendency to take the path of least resistance. It demonstrates that as long as there is a human in the loop, the adversary will find a way to manipulate that person into opening the door, no matter how many locks we put on it. The “official” email is merely the first step in a psychological siege designed to break the victim’s resolve.
The strategy of the modern phisher has moved beyond the simple theft of credentials and into the territory of high-stakes narrative control. When we analyze the rise of Business Email Compromise, it becomes clear that the “Official” email is often just the opening act in a long-form con that can last for weeks. The attacker doesn’t just want a password; they want to insert themselves into the financial workflow of an organization. By mimicking the tone, the signature blocks, and the specific jargon of a vendor or a high-level partner, the adversary creates a secondary reality where a change in banking details or a diverted wire transfer seems like a routine administrative adjustment. The horror of this approach lies in its banality. There are no flashing red lights or “Access Denied” screens; there is only a quiet, professional-looking email that follows every established rule of corporate etiquette while it drains the company’s accounts.
Furthermore, the integration of generative AI into the attacker’s toolkit has eliminated the last remaining red flags that used to give these “Official” lures away. Gone are the days when a sharp-eyed employee could spot a phishing attempt by its poor grammar or awkward phrasing. Today’s lures are syntactically perfect, culturally nuanced, and tailored to the specific industry of the target. An attacker can now feed a few public interviews or LinkedIn posts from an executive into a model and generate an email that captures that individual’s unique “voice” with terrifying precision. This makes the “Official” email even more dangerous because it appeals to the victim’s sense of familiarity. Consequently, the gap between a legitimate internal communication and a fraudulent one has narrowed to the point of invisibility, leaving the human target to navigate a minefield where every step looks like solid ground.
The Weaponization of Compliance and Legal Fear
A significant portion of why people still fall for these lures is the strategic use of “regulatory theater” to induce a state of compliance-driven panic. Attackers have realized that the modern professional is terrified of three things: HR violations, tax audits, and data breaches. By framing a phishing lure as a “Mandatory Data Privacy Attestation” or an “Immediate Tax Compliance Notice,” the attacker leverages the weight of the law to bypass the user’s skepticism. These emails often include realistic references to actual legislation, such as GDPR or the CCPA, which adds a layer of superficial credibility that is hard to ignore. The victim isn’t just clicking a link; they are attempting to protect themselves or their company from a perceived legal threat. This flip of the script—making the scam look like a security measure—is a calculated move that turns a person’s best intentions into their greatest vulnerability.
In addition to legal threats, the “Official” lure often exploits the internal power dynamics of the modern workplace. In a high-pressure environment where “performance” is everything, the fear of failing to respond to a superior is a powerful motivator. I see this play out in “Urgent Request” scenarios where the email appears to come from a CEO or a Board Member who is “stuck in a meeting” and needs a quick favor. The victim is often so focused on the social reward of being helpful or the fear of appearing incompetent that they fail to perform even basic due diligence. The adversary knows that in a hierarchy, authority flows downward with a force that can flatten common sense. By the time the employee thinks to call the executive to verify the request, the gift cards have been drained or the sensitive spreadsheet has been uploaded to a command-and-control server.
Rebuilding the Perimeter on a Foundation of Radical Skepticism
If we are going to survive in this environment, we have to move past the idea that we can train the human element out of the equation. The “Official” email works because it is designed to work on humans, and humans are fundamentally social, cooperative, and prone to pressure. The solution isn’t another hour of boring slide decks; it’s a fundamental shift toward an “Assume Breach” mentality at the individual level. This means moving away from a culture of blind trust and toward one of verified communication, where no request involving data or money is ever handled through a single, unverified channel. We need to normalize the “Double-Check”—the idea that calling a coworker to verify an unusual email is not a sign of paranoia, but a standard operating procedure. This cultural shift is far harder to implement than a new firewall, but it is the only thing that can stand against the psychological precision of the modern phisher.
Moreover, organizations must stop relying on the visual “polish” of an email as a proxy for its legitimacy. We need to strip away the corporate logos and the fancy signatures in our minds and look at the raw intent of the message. If an email creates a sense of urgency, demands a bypass of standard procedures, or directs you to an external site to enter credentials, it should be treated as hostile until proven otherwise. The “Official” email is a mask, and the only way to beat it is to stop being impressed by the mask. We have to start valuing the friction in our systems—the extra steps, the out-of-band verifications, and the healthy skepticism—because that friction is the only thing that slows the attacker down long enough for us to see the hook beneath the bait. The rain is still falling on the digital asphalt, and the shadows are still reaching, but they only win when we let them lead us where they want us to go.
The persistence of the “Official” email as a top-tier threat vector is ultimately a testament to the fact that technical solutions are being applied to a non-technical problem. We are trying to use cryptographic signatures and automated filters to solve for the human desire to be helpful, the fear of authority, and the exhaustion of the modern workday. It is a mismatch of resources that the adversary exploits with predatory efficiency. When I look at the wreckage left behind by these campaigns, it is rarely the result of a single catastrophic failure; rather, it is a series of small, logical concessions made by a tired person just trying to get through their inbox. The attacker doesn’t need to be a digital ghost or a coding prodigy; they just need to be a better actor than you are a skeptic. They understand that if they can control the narrative, they can control the network, and they use the “Official” branding as the stage on which they perform their heist.
To break this cycle, we have to stop treating phishing as a “user error” and start treating it as an inevitable environmental hazard. This requires a defensive architecture that doesn’t just look for bad files, but looks for suspicious behaviors and anomalies in the flow of authority. If an executive who never handles wire transfers suddenly sends an “Official” urgent request for one, the system should be smart enough to flag the deviation, regardless of how clean the email headers look. We need to build systems that protect people from their own instinct to comply, creating hard stops and out-of-band verification requirements for any high-value transaction. The goal is to move the burden of defense off the shoulders of the individual and into the design of the workflow itself. Until we accept that the “Official” email is the most dangerous weapon in the digital world, we will continue to find ourselves staring at the empty accounts and compromised servers that are the hallmark of a successful hook, line, and sinker.
Call to Action
The time for treating phishing as a minor IT nuisance is over; it is a predatory psychological war, and you are currently the primary target. If you are a leader, you need to stop hiding behind automated filters and start building a culture where a healthy “no” is valued more than a rushed “yes.” Stop the assembly line long enough to verify the source, pick up the phone when an email feels even slightly off-kilter, and demand that your organization implements out-of-band verification for every high-stakes transaction. Don’t wait for the post-mortem report to realize your “official” communication was a ghost in the machine. Audit your workflows today, tighten your authentication protocols, and train your eyes to see the hook beneath the polish—because the next “urgent” email in your inbox isn’t looking to help you, it’s looking to gut you.
SUPPORTSUBSCRIBECONTACT MED. Bryan King
Sources
- FBI IC3 2023 Internet Crime Report
- Verizon 2024 Data Breach Investigations Report (DBIR)
- CISA: Phishing Campaigns Targeting Government Entities
- Microsoft Digital Defense Report: The Evolution of Phishing
- Proofpoint 2024 State of the Phish Report
- ENISA Threat Landscape 2023
- NIST SP 800-63 Digital Identity Guidelines
- Trellix Cyber Readiness Report: Email Security Trends
- KnowBe4 2023 Phishing by Industry Benchmarking Report
- IBM Cost of a Data Breach Report 2023
- Unit 42 Cloud Threat Report: Credential Harvesting
- CrowdStrike 2024 Global Threat Report
- Zscaler ThreatLabz 2023 Phishing Report
- Mandiant M-Trends 2024 Special Report
- Dark Reading: How Modern Phishing Bypasses MFA
- BleepingComputer: AiTM Phishing Kits Targeting M365
- SecurityWeek: BEC Attacks Leveraging Generative AI
- Wired: The Psychology Behind the Phish
- SANS Institute: Defeating Social Engineering in the Modern Office
- ZDNet: Anatomy of a BEC Attack
- Kroll Q3 2023 Cyber Threat Landscape
- McAfee Labs: The Science of Social Engineering
- F-Secure: How Criminals Exploit Human Emotions
- Kaspersky: Spam and Phishing in 2023 Analysis
- Sophos 2023 Active Adversary Report
- SC Magazine: Phishing as a Ransomware Vector
- Threatpost: Business Email Compromise – The Invisible Threat
- Infosecurity Magazine: AI-Generated Phishing Success Rates
- CSO Online: Psychological Principles Attackers Exploit
- Help Net Security: The Democratization of Phishing Kits
- Fortinet: The Evolution of Spear Phishing
- Check Point: Common Phishing Examples and Tactics
- Rapid7: Fundamentals of Phishing and Social Engineering
- Malwarebytes: Why People Click on Malicious Links
- Bitdefender Labs: Targeting Financial Institutions
- Trend Micro: The Art of the Lure
- ESET 2023 Phishing Trends Report
- Symantec: Phishing Tactics That Evade Detection
- Cloudflare: What is Phishing? Guide for Teams
- IT Governance: Top 5 Phishing Scams of 2023
Disclaimer:
The views and opinions expressed in this post are solely those of the author. The information provided is based on personal research, experience, and understanding of the subject matter at the time of writing. Readers should consult relevant experts or authorities for specific guidance related to their unique situations.
Related Posts
Rate this:
#adversaryInTheMiddle #AiTM #AuthorityBias #BEC #businessEmailCompromise #CEOFraud #CognitiveLoad #corporateEspionage #corporateSecurity #credentialHarvesting #cyberDefense #cyberResilience #cyberRiskManagement #cyberThreats #cybercrime #cybersecurityBlog #cybersecurityTraining #dataBreach #DigitalAmbush #DKIM #DMARC #DocuSignScams #emailSecurity #financialFraud #HumanError #identityTheft #incidentResponse #informationSecurity #IRSPhishing #LivingOffTheLand #MalwareFreeAttacks #MFABypass #MFAFatigue #Microsoft365Security #OfficialEmailScams #phishing #PsychologicalExploitation #RegulatoryPhishing #secureEmailGateway #securityAwareness #SecurityNihilism #sessionHijacking #SharePointPhishing #socialEngineering #spearPhishing #SPF #threatIntelligence #TrustArchitecture #UrgencyTactics #vendorImpersonation #zeroTrust -
⚠️ Extensions hijack sessions instead of just stealing data At least 12 fake #TikTok downloader extensions inject scripts to capture Facebook session cookies, enabling full account takeover without credentials across Chrome and Edge installs. #ransomNews #BrowserSecurity #SessionHijacking
-
⚠️ Extensions hijack sessions instead of just stealing data At least 12 fake #TikTok downloader extensions inject scripts to capture Facebook session cookies, enabling full account takeover without credentials across Chrome and Edge installs. #ransomNews #BrowserSecurity #SessionHijacking
-
Taboola Exploits Banking Sessions to Route Users to Temu Tracking Endpoint
Imagine a single line of code secretly redirecting people logged into their bank accounts to a commercial tracking site - that's what happened when a bank unknowingly approved a Taboola pixel that sent users to a Temu tracking endpoint. This sneaky exploit slipped past security controls, leaving both the bank and…
#ThirdpartyRisk #SupplyChain #SessionHijacking #TrackingExploit #BankingSecurity
-
Storm Infostealer Exploits Server-Side Decryption for Session Hijacking
Imagine if hackers could hijack your online sessions, bypassing even the strongest passwords and multifactor protections - a new infostealer called Storm makes this a chilling reality by exploiting server-side decryption to steal sensitive browser data. This sneaky malware allows attackers to take over your…
#StormInfostealer #SessionHijacking #MfaBypass #Infostealer #ServersideDecryption
-
Google Deploys DBSC in Chrome to Thwart Windows Session Hijacking
Google just flipped the switch on Device Bound Session Credentials (DBSC) for Chrome users on Windows, giving millions a major security boost against session hijacking - but what does it mean for you? This game-changing update ties your credentials to your device, making it much harder for hackers to get hold of…
#DeviceBoundSessionCredentials #GoogleChrome #Windows #SessionHijacking #EmergingThreats
-
📬 Storm Infostealer umgeht 2FA: Malware übernimmt Accounts ohne Passwort
#DarkCommerce #Malware #2FAumgehen #AccountÜbernahme #BrowserDatenklau #Cybercrime #Datendiebstahl #Infostealer #MalwareasaService #SessionHijacking #StormInfostealer https://sc.tarnkappe.info/d93668 -
📬 Storm Infostealer umgeht 2FA: Malware übernimmt Accounts ohne Passwort
#DarkCommerce #Malware #2FAumgehen #AccountÜbernahme #BrowserDatenklau #Cybercrime #Datendiebstahl #Infostealer #MalwareasaService #SessionHijacking #StormInfostealer https://sc.tarnkappe.info/d93668 -
Microsoft Authenticator’s Unclaimed Deep Link: A Full Account Takeover Story (CVE-2026–26123)
This vulnerability is an Authentication Bypass, specifically a session hijacking issue affecting the Microsoft Authenticator app. The root cause was improper handling of deep links within the application, which allowed malicious actors to craft unclaimed deep links containing account tokens. When users clicked these links, their active sessions were hijacked, resulting in full account takeover without requiring any user interaction other than clicking a link. To exploit this, an attacker could generate a malicious deep link with an embedded account token and share it via SMS or email. The session hijack occurred due to the application's failure to verify the authenticity of deep links before processing them. This vulnerability has been assigned CVE-2026–26123. Microsoft rewarded $50,000 for this find and immediately patched the issue. To prevent similar vulnerabilities, it is crucial to thoroughly validate and sanitize all user-controlled inputs, including deep links. Key lesson: Always verify the authenticity of user-supplied data before processing it. #BugBounty #Cybersecurity #AuthenticationBypass #SessionHijacking #Infosec -
Microsoft Authenticator’s Unclaimed Deep Link: A Full Account Takeover Story (CVE-2026–26123)
This vulnerability is an Authentication Bypass, specifically a session hijacking issue affecting the Microsoft Authenticator app. The root cause was improper handling of deep links within the application, which allowed malicious actors to craft unclaimed deep links containing account tokens. When users clicked these links, their active sessions were hijacked, resulting in full account takeover without requiring any user interaction other than clicking a link. To exploit this, an attacker could generate a malicious deep link with an embedded account token and share it via SMS or email. The session hijack occurred due to the application's failure to verify the authenticity of deep links before processing them. This vulnerability has been assigned CVE-2026–26123. Microsoft rewarded $50,000 for this find and immediately patched the issue. To prevent similar vulnerabilities, it is crucial to thoroughly validate and sanitize all user-controlled inputs, including deep links. Key lesson: Always verify the authenticity of user-supplied data before processing it. #BugBounty #Cybersecurity #AuthenticationBypass #SessionHijacking #Infosec -
Bad actors are creating browser extensions that claim to be ChatGPT productivity tools, but that steal your account credentials and hijack sessions instead.
While researchers can find and warn us about these malicious extensions, it’s important to recognize that we’re about to enter an era where this kind of behavior is actually relied on by good actors (read: agents) as well. It’s imperative that we work on developing alternatives to this.
#Security #TokenHijacking #SessionHijacking
https://www.bitdefender.com/en-us/blog/hotforsecurity/beware-fake-chatgpt-browser-extensions-are-stealing-your-login-credentials -
Bad actors are creating browser extensions that claim to be ChatGPT productivity tools, but that steal your account credentials and hijack sessions instead.
While researchers can find and warn us about these malicious extensions, it’s important to recognize that we’re about to enter an era where this kind of behavior is actually relied on by good actors (read: agents) as well. It’s imperative that we work on developing alternatives to this.
#Security #TokenHijacking #SessionHijacking
https://www.bitdefender.com/en-us/blog/hotforsecurity/beware-fake-chatgpt-browser-extensions-are-stealing-your-login-credentials -
More than 4.3 million users were affected before anyone realized ShadyPanda’s extensions had turned into full surveillance tools.
In the latest Cyberside Chats episode, Sherri Davidoff and Matt Durrin break down how attackers built trust for years, then used auto-updates to harvest browsing data, authentication tokens, and even live session cookies. The discussion also covers why session hijacking is so dangerous—and the safeguards security leaders should be implementing now.
Watch the full conversation: https://youtu.be/x9AaE94KanM
Or listen to the podcast: https://www.chatcyberside.com/e/shady-panda-s-browser-backdoor-%E2%80%94-43m-chrome-edge-users-compromised/
#CybersideChats #BrowserSecurity #SupplyChainRisk #SessionHijacking #CyberThreats #IdentitySecurity #EnterpriseSecurity #SecurityOperations
-
📬 Pi-hole XSS CVE-2025-53533: kritische Sicherheitslücke entdeckt
#Cyberangriffe #ITSicherheit #AdministrationsZugriff #CookieDiebstahl #CVE202553533 #PiHole #SessionHijacking #TemplateFehler #XSSFehler https://sc.tarnkappe.info/182aaf -
📬 Pi-hole XSS CVE-2025-53533: kritische Sicherheitslücke entdeckt
#Cyberangriffe #ITSicherheit #AdministrationsZugriff #CookieDiebstahl #CVE202553533 #PiHole #SessionHijacking #TemplateFehler #XSSFehler https://sc.tarnkappe.info/182aaf -
Google Debuts Device-Bound Session Credentials Against Session Hijacking
#HackerNews #Google #Device-Bound #Credentials #SessionHijacking #CyberSecurity #TechNews
-
Google Debuts Device-Bound Session Credentials Against Session Hijacking
#HackerNews #Google #Device-Bound #Credentials #SessionHijacking #CyberSecurity #TechNews
-
High Severity Vulnerability Discovered in CP Plus Router: Immediate Attention Needed https://thecyberexpress.com/cp-plus-router-vulnerability/ #CPPlusRouterVulnerability #TheCyberExpressNews #SessionHijacking #Vulnerabilities #CPPlusCPXRDE21S #TheCyberExpress #FirewallDaily #CIVN20250005 #HTTPsession #CyberNews
-
High Severity Vulnerability Discovered in CP Plus Router: Immediate Attention Needed https://thecyberexpress.com/cp-plus-router-vulnerability/ #CPPlusRouterVulnerability #TheCyberExpressNews #SessionHijacking #Vulnerabilities #CPPlusCPXRDE21S #TheCyberExpress #FirewallDaily #CIVN20250005 #HTTPsession #CyberNews
-
Hackers Can Hijack Your MFA Enabled Email Accounts By Stealing Cookies https://cybersecuritynews.com/hackers-hijack-mfa-enabled/ #CybersecurityThreats #SessionHijacking #CyberSecurity #Threats #Email
-
Hackers Can Hijack Your MFA Enabled Email Accounts By Stealing Cookies https://cybersecuritynews.com/hackers-hijack-mfa-enabled/ #CybersecurityThreats #SessionHijacking #CyberSecurity #Threats #Email
-
As always the information in this thread as well as more can be found in my notes at: https://notes.zanidd.xyz/
Thank you for reading my thread and see you in the next one :)
-
As always the information in this thread as well as more can be found in my notes at: https://notes.zanidd.xyz/
Thank you for reading my thread and see you in the next one :)
-
Remediating Open Redirect
- Strictly validate URLs
- Do not use user-supplied URLs
- Check supplied values (valid, not an URL, appropriate for the app)
- Sanitize input with an allowlist of trusted hosts (or regex)
- Force redirects to first go through a page notifying users that they're leaving the site
#cybersecurity #session #csrf #xss #sessionhijacking #sessionfixation
-
Remediating Open Redirect
- Strictly validate URLs
- Do not use user-supplied URLs
- Check supplied values (valid, not an URL, appropriate for the app)
- Sanitize input with an allowlist of trusted hosts (or regex)
- Force redirects to first go through a page notifying users that they're leaving the site
#cybersecurity #session #csrf #xss #sessionhijacking #sessionfixation
-
Remediating CSRF
- Check if user is authorized to perform action
- Add randomly generated + non-predictable tokens (anti-csrf-token, csrf-tokens)
- Referrer Header Checking
- Implement Two-Step operation (Operation is not executed when called, but needs a verification)
- Make Cookies SameSite!
#cybersecurity #session #csrf #xss #sessionhijacking #sessionfixation
-
Remediating CSRF
- Check if user is authorized to perform action
- Add randomly generated + non-predictable tokens (anti-csrf-token, csrf-tokens)
- Referrer Header Checking
- Implement Two-Step operation (Operation is not executed when called, but needs a verification)
- Make Cookies SameSite!
#cybersecurity #session #csrf #xss #sessionhijacking #sessionfixation
-
Remediating XSS
- Validation of user input (on the server side)
- Use positive approach (allowlist)
- verify existence of actual Input
- Enforce Input Size restriction
- Check Input Type and only allow certain types
- Check range of value and restrict it
- Sanitize special chars
- HTML Encoding Output (especially user-controlled output)
- Do not embed user input into client-side scripts
- Have a good CSP (Content Security Policy)
- Make Cookies HTTPOnly!
#cybersecurity #session #csrf #xss #sessionhijacking #sessionfixation
- Validation of user input (on the server side)
-
Remediating XSS
- Validation of user input (on the server side)
- Use positive approach (allowlist)
- verify existence of actual Input
- Enforce Input Size restriction
- Check Input Type and only allow certain types
- Check range of value and restrict it
- Sanitize special chars
- HTML Encoding Output (especially user-controlled output)
- Do not embed user input into client-side scripts
- Have a good CSP (Content Security Policy)
- Make Cookies HTTPOnly!
#cybersecurity #session #csrf #xss #sessionhijacking #sessionfixation
- Validation of user input (on the server side)
-
Remediation Session Fixation
- Generate new session ID after authenticated operation (invalidate pre-login session id and generate a new one post-login)
- use libraries and built in mechanisms for session management, don't build custom implementations
Example Function for PHP:
session_regenerate_id(bool $delete_old_session = false): bool#cybersecurity #session #csrf #xss #sessionhijacking #sessionfixation
-
Remediation Session Fixation
- Generate new session ID after authenticated operation (invalidate pre-login session id and generate a new one post-login)
- use libraries and built in mechanisms for session management, don't build custom implementations
Example Function for PHP:
session_regenerate_id(bool $delete_old_session = false): bool#cybersecurity #session #csrf #xss #sessionhijacking #sessionfixation
-
Remediating Session Hijacking
- Pretty challenging to counter session hijacking
- Monitoring + Anomaly Detection
- safer bet to counter than to eliminate all vulns
#hacking #cybersecurity #session #csrf #xss #sessionhijacking #sessionfixation
-
Remediating Session Hijacking
- Pretty challenging to counter session hijacking
- Monitoring + Anomaly Detection
- safer bet to counter than to eliminate all vulns
#hacking #cybersecurity #session #csrf #xss #sessionhijacking #sessionfixation
-
Here is some Advice on how to remediate common Session Security Attacks/Vulns (based on HTB Academy).
1/? 🧵
#hacking #cybersecurity #session #csrf #xss #sessionhijacking #sessionfixation
-
Here is some Advice on how to remediate common Session Security Attacks/Vulns (based on HTB Academy).
1/? 🧵
#hacking #cybersecurity #session #csrf #xss #sessionhijacking #sessionfixation
-
I came across Headlines trying to introduce fear of #FIDO2.
"Using MITM to bypass FIDO2 phishing-resistant protection" and "Passwordless Authentication Standard FIDO2 Flaw Let Attackers Launch MITM Attacks" seem very frightening. So I took a closer look into those articles.
https://www.silverfort.com/blog/using-mitm-to-bypass-fido2/
https://gbhackers.com/fid02-mitm-vulnerability/They seem very much identical down to the fact they use the same illustrations. My understanding is that the demonstrated "#MITM #Attack" is actually an attack on the session coockie. So The idea is to let the #FIDO2 #Authentication take place uninterrupted and when successful, intercept the Session cockie when sent from the Relaying Party/Webserver to the client.
Maybe someone with a better understanding of the Standards can correct me but this attack looks to me as if it only attackls the session information which would be possible no mather what authentication would be used. In my understanding, secure session handling is a real thread but outside of the actual FIDO2 scope.
What do you think? Is it FIDO2 related? Or just a generic Session Session hijacking that happens to work besides others also with FIDO2 authentications?
-
Should security features be planned in web applications at an early stage? We believe so.
In this third article on best practices for app developers, we conclude the discussion on how to prevent session hijacking with a series of recommendations for application design.#bestpractices #appdesign #secureapps #appsecurity #sessionhijacking #negativepid
-
XSS Vulnerability in Google Subdomain Let Hackers Hijack User Sessions
Date: March 15, 2024
CVE: Not specified
Sources: Cyber Security NewsIssue Summary
A significant XSS vulnerability was found in the
aihub.cloud.google.comsubdomain by Henry N. Caga, enabling potential session hijacking, phishing, malware distribution, and data theft. Initially hard to replicate, persistence and a double-encoded payload exposed the flaw affecting URLs with aqparameter.Technical Key findings
The flaw was discovered after testing various payloads on the
qparameter, with double encoding revealing the vulnerability across all URLs under the affected domain.Vulnerable products
- aihub.cloud.google.com domain
Impact assessment
Risks included session hijacking, phishing attacks, malware distribution, and sensitive data theft, potentially damaging Google's reputation.
Patches or workaround
Google addressed the vulnerability, rewarding Caga $4,133.70, including a $1,000 bonus for his detailed report and proof of concept.
Tags
#XSS #Google #CyberSecurity #SessionHijacking #Phishing #Malware
-
XSS Vulnerability in Google Subdomain Let Hackers Hijack User Sessions
Date: March 15, 2024
CVE: Not specified
Sources: Cyber Security NewsIssue Summary
A significant XSS vulnerability was found in the
aihub.cloud.google.comsubdomain by Henry N. Caga, enabling potential session hijacking, phishing, malware distribution, and data theft. Initially hard to replicate, persistence and a double-encoded payload exposed the flaw affecting URLs with aqparameter.Technical Key findings
The flaw was discovered after testing various payloads on the
qparameter, with double encoding revealing the vulnerability across all URLs under the affected domain.Vulnerable products
- aihub.cloud.google.com domain
Impact assessment
Risks included session hijacking, phishing attacks, malware distribution, and sensitive data theft, potentially damaging Google's reputation.
Patches or workaround
Google addressed the vulnerability, rewarding Caga $4,133.70, including a $1,000 bonus for his detailed report and proof of concept.
Tags
#XSS #Google #CyberSecurity #SessionHijacking #Phishing #Malware
-
FlowFixation: AWS Apache Airflow Service Takeover Vulnerability
Date: March 21, 2024
CVE: Not specified
Sources: Tenable BlogIssue Summary
Tenable Research discovered a vulnerability, named FlowFixation, in AWS Managed Workflows for Apache Airflow (MWAA) that could allow session hijacking leading to a full takeover of the victim's web management panel.
Technical Key findings
FlowFixation combines session fixation and XSS via Amazon AWS domain misconfiguration, enabling attackers to authenticate known sessions and gain control over victim's Apache Airflow management panels.
Vulnerable products
- AWS Managed Workflows for Apache Airflow (MWAA)
Impact assessment
Potential for remote code execution on underlying instances and lateral movement to other services.
Patches or workaround
AWS has addressed the vulnerability. Users should ensure they are using updated services.
Tags
#AWS #ApacheAirflow #CloudSecurity #SessionHijacking #Vulnerability
-
FlowFixation: AWS Apache Airflow Service Takeover Vulnerability
Date: March 21, 2024
CVE: Not specified
Sources: Tenable BlogIssue Summary
Tenable Research discovered a vulnerability, named FlowFixation, in AWS Managed Workflows for Apache Airflow (MWAA) that could allow session hijacking leading to a full takeover of the victim's web management panel.
Technical Key findings
FlowFixation combines session fixation and XSS via Amazon AWS domain misconfiguration, enabling attackers to authenticate known sessions and gain control over victim's Apache Airflow management panels.
Vulnerable products
- AWS Managed Workflows for Apache Airflow (MWAA)
Impact assessment
Potential for remote code execution on underlying instances and lateral movement to other services.
Patches or workaround
AWS has addressed the vulnerability. Users should ensure they are using updated services.
Tags
#AWS #ApacheAirflow #CloudSecurity #SessionHijacking #Vulnerability
-
@11110110101 @heiseonline
Wenn ich das Original (https://www.cloudsek.com/blog/compromising-google-accounts-malwares-exploiting-undocumented-oauth2-functionality-for-session-hijacking) richtig lese, besteht das Problem nur für schon geknackt Accounts. Vermutlich hilft MFA, damit es gar nicht so weit kommt?Sonst:
"If you suspect your account may have been compromised, or as a general precaution, sign out of all browser profiles to invalidate the current session tokens. Following this, reset your password and sign back in to generate new tokens." -
We need browser profile primary password logins to help prevent session hijacking
Seeing what happened this week to the Linus Tech Tips YouTube channel made me realise how well we have secured in transit data, password managers, etc (LastPass was also hacked via an end user session) but we appear to have the session data left wide open on ...continues
-
We need browser profile primary password logins to help prevent session hijacking
Seeing what happened this week to the Linus Tech Tips YouTube channel made me realise how well we have secured in transit data, password managers, etc (LastPass was also hacked via an end user session) but we appear to have the session data left wide open on ...continues
-
Seeing what happened this week to the Linus Tech Tips YouTube channel made me realise how well we have secured in transit data, password managers, etc (LastPass was also hacked via an end user session) but we appear to have the session data left wide open on our local machines.
I see that Firefox and Edge have profile logins, but mainly to protect the login passwords. Most Chromium based browsers do have profiles, but do not even appear to have any form of login attached to them.
Surely not just the logins can be protected, and we could have 1st party and session cookie access also protected behind a profile password? Whenever you start up your browser the first time, you are prompted for the profile primary password to unlock access to passwords, extension data, and cookies? In this way, if some bad (or good) actor stole your session data (the session data would be in use and unlocked), they'd still be prompted for a password before being able to actually use it on a freshly started browser elsewhere?
Maybe this is not the best way to do it, but clearly some improvement is needed to protect against this form of data hijacking.
#technology #security #sessionhijacking #browers -
We need browser profile primary password logins to help prevent session hijacking
https://gadgeteer.co.za/wp-content/uploads/2023/03/Screenshot_20230324_140123-400x323.jpg Seeing what happened this week to the Linus Tech Tips YouTube channel made me realise how well we have secured in transit data, password managers, etc (LastPass was also hacked via an end user session) […]
https://squeet.me/display/962c3e10-80792827-8fec9710a8f6040c
