home.social

#sessionhijacking — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #sessionhijacking, aggregated by home.social.

fetched live
  1. Sellers advertise 'Remus', a $1,000 tool allegedly maintaining Gmail access after password resets via session or token persistence. If validated, it would undermine standard recovery assumptions and enable prolonged email compromise. #GmailSecurity #SessionHijacking #InfoSec

    cyberworldops.eu/en/remus-sell

  2. اختراق CircleCI وسرقة جلسة مصادق عليها

    🔹 1- الجهة المستهدفة (Target Entity): شركة CircleCI وعملاؤها الذين يستخدمون منصة CI/CD. 🔹 2- نوع الهجوم (Attack Type): Endpoint Malware / Session Cookie Theft / Session Hijacking. 🔹 3- كيف تم الهجوم (Attack Execution): أصيب جهاز أحد المهندسين ببرمجية خبيثة سرقت Session Cookie لجلسة SSO سبق توثيقها باستخدام MFA. استخدم المهاجم الجلسة […]

    cybercases8.wordpress.com/2026

  3. Sentence: Revoke suspicious Google sessions, audit active cookies, and enforce hardware security keys immediately.

    Reward: You've received a Contempt of Courthouse Badge and absolutely zero sympathy from this bench.

    #Malware #CyberSecurity #SessionHijacking #Cryptocurrency #AuthenticationBypass #CookieMonster (3/3)

  4. Anthropic has begun notifying users that infostealer malware on their endpoints captured active Claude session tokens. This allowed attackers to bypass both password and 2FA controls, leading to unauthorized account access and consumption of paid credits.

    #SessionHijacking #Infostealer #Anthropic #CredentialTheft

    cyberworldops.eu/en/claude-ses

  5. Anthropic Warns of Infostealer Malware Hijacking Claude Sessions

    Beware of infostealer malware that's hijacking Claude sessions! Anthropic is taking swift action to protect users, including signing them out of compromised accounts, removing saved payment methods, and offering refunds for unauthorized charges.

    osintsights.com/anthropic-warn

    #InfostealerMalware #EmergingThreats #AiSecurity #SessionHijacking #MalwareOperations

  6. ⚠️ 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

  7. 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

    infosecwriteups.com/microsoft-

  8. 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
    bitdefender.com/en-us/blog/hot

  9. 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: youtu.be/x9AaE94KanM

    Or listen to the podcast: chatcyberside.com/e/shady-pand

    #CybersideChats #BrowserSecurity #SupplyChainRisk #SessionHijacking #CyberThreats #IdentitySecurity #EnterpriseSecurity #SecurityOperations

  10. NCL Web Application Challenge: Infosec Blog — CTF Write-Up NCL Web Application Challenge: Infosec Blog — CTF Write-Up Category: Web Application Challenge Name: Infosec Blog Difficulty...

    #ctf-writeup #session-token #cryptography #web-application-security #session-hijacking

    Origin | Interest | Match
  11. Session Hijacking: How Weak Authentication Destroys Security in 2025 The digital world operates on trust — trust that when users log into their banking app, their email, or their company’s ...

    #information-technology #session-hijacking #cybersecurity #information-security #cyber-security-awareness

    Origin | Interest | Match
  12. As always the information in this thread as well as more can be found in my notes at: notes.zanidd.xyz/

    Thank you for reading my thread and see you in the next one :)

    #session #csrf #xss #sessionhijacking #sessionfixation

  13. 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

  14. 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

  15. 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

  16. 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

  17. 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

  18. 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

  19. 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.

    silverfort.com/blog/using-mitm
    gbhackers.com/fid02-mitm-vulne

    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?

    #FIDO2 #Attack #MITM #Flaw #sessionhijacking

  20. XSS Vulnerability in Google Subdomain Let Hackers Hijack User Sessions

    Date: March 15, 2024

    CVE: Not specified

    Sources: Cyber Security News

    Issue Summary

    A significant XSS vulnerability was found in the aihub.cloud.google.com subdomain 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 a q parameter.

    Technical Key findings

    The flaw was discovered after testing various payloads on the q parameter, 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

  21. FlowFixation: AWS Apache Airflow Service Takeover Vulnerability

    Date: March 21, 2024
    CVE: Not specified
    Sources: Tenable Blog

    Issue 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

  22. @11110110101 @heiseonline
    Wenn ich das Original (cloudsek.com/blog/compromising) 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."

    #Google #MFA #OAuth #SessionHijacking #SessionCookies

  23. 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

    See gadgeteer.co.za/we-need-browse

    #browsers #security #sessionhijacking #technology

  24. 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

  25. We need browser profile primary password logins to help prevent session hijacking

    gadgeteer.co.za/wp-content/upl 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) […]

    gadgeteer.co.za/we-need-browse

    squeet.me/display/962c3e10-807

Share on Mastodon

Enter the server where you have an account.