Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Tìm kiếm hỗ trợ

Tránh các lừa đảo về hỗ trợ. Chúng tôi sẽ không bao giờ yêu cầu bạn gọi hoặc nhắn tin đến số điện thoại hoặc chia sẻ thông tin cá nhân. Vui lòng báo cáo hoạt động đáng ngờ bằng cách sử dụng tùy chọn "Báo cáo lạm dụng".

Tìm hiểu thêm

Hacked flagrantly

  • 1 trả lời
  • 0 gặp vấn đề này
  • Trả lời mới nhất được viết bởi Denys
  • Đã khóa

To the Security and Privacy Compliance Team: I am formally reporting a severe security breach affecting my account(s) and digital environment. Despite strict adherence to security protocols—including the use of two-factor authentication (2FA), non-reused/secure passwords, and active monitoring with Malwarebytes—my environment has been consistently manipulated by unauthorized automated processes. Summary of Compromise: This is not a case of user error. My environment shows clear evidence of session token hijacking and automated configuration tampering. Specifically, my sessions are being forced into unauthorized linkages (e.g., Google OAuth backdoors) that I have explicitly revoked. Technical Evidence of Interference: 1 System-Level Artifacts: My browser instances (Safari/Firefox) have been rendered non-functional (failing to load pages) for an extended period, yet these applications continue to generate "browsing history" and metadata. This metadata is fraudulent—it is machine-generated output, not user-initiated activity. 2 Unauthorized OAuth Linkages: I have documented instances where 2FA-secured accounts were bypassed through the injection of secondary identity tokens (linking to an ainsleyhenn2024@gmail.com identity I did not authorize). 3 Malwarebytes Forensic Logs: I have attached logs from Malwarebytes, which provide objective, non-tampered evidence of blocked connections and attempted malicious interference that occurred simultaneously with the "bizarre" browser behavior I have witnessed. 4 Credential Bypassing: The behavior observed indicates a bypass of standard authentication flows. This suggests either a compromise of the authentication delivery service (the "Mail app" shell hijacking) or the deployment of a corrupted/compromised version of your software. Formal Request for Forensic Audit: The persistence of this activity suggests a systemic flaw or a compromised session pipeline. I request a Session Token Audit to identify:

The specific IP addresses and device fingerprints that initiated the unauthorized linkage of the Gmail identity to my account.
The OAuth scope granted during these automated handshakes.

Offer of Facilitation: I am documenting these issues in detail and have retained all relevant diagnostic logs. I am prepared to share these logs to facilitate a forensic examination, provided this inquiry is escalated to your Security or Data Integrity team. I am seeking a resolution that addresses the systemic failure to protect my data and ensures my account integrity is restored to a trusted state. Please advise on the secure channel for submitting this technical evidence for a full forensic review.

To the Security and Privacy Compliance Team: I am formally reporting a severe security breach affecting my account(s) and digital environment. Despite strict adherence to security protocols—including the use of two-factor authentication (2FA), non-reused/secure passwords, and active monitoring with Malwarebytes—my environment has been consistently manipulated by unauthorized automated processes. Summary of Compromise: This is not a case of user error. My environment shows clear evidence of session token hijacking and automated configuration tampering. Specifically, my sessions are being forced into unauthorized linkages (e.g., Google OAuth backdoors) that I have explicitly revoked. Technical Evidence of Interference: 1 System-Level Artifacts: My browser instances (Safari/Firefox) have been rendered non-functional (failing to load pages) for an extended period, yet these applications continue to generate "browsing history" and metadata. This metadata is fraudulent—it is machine-generated output, not user-initiated activity. 2 Unauthorized OAuth Linkages: I have documented instances where 2FA-secured accounts were bypassed through the injection of secondary identity tokens (linking to an ⁠ainsleyhenn2024@gmail.com⁠ identity I did not authorize). 3 Malwarebytes Forensic Logs: I have attached logs from Malwarebytes, which provide objective, non-tampered evidence of blocked connections and attempted malicious interference that occurred simultaneously with the "bizarre" browser behavior I have witnessed. 4 Credential Bypassing: The behavior observed indicates a bypass of standard authentication flows. This suggests either a compromise of the authentication delivery service (the "Mail app" shell hijacking) or the deployment of a corrupted/compromised version of your software. Formal Request for Forensic Audit: The persistence of this activity suggests a systemic flaw or a compromised session pipeline. I request a Session Token Audit to identify: The specific IP addresses and device fingerprints that initiated the unauthorized linkage of the Gmail identity to my account. The OAuth scope granted during these automated handshakes. Offer of Facilitation: I am documenting these issues in detail and have retained all relevant diagnostic logs. I am prepared to share these logs to facilitate a forensic examination, provided this inquiry is escalated to your Security or Data Integrity team. I am seeking a resolution that addresses the systemic failure to protect my data and ensures my account integrity is restored to a trusted state. Please advise on the secure channel for submitting this technical evidence for a full forensic review.

Tất cả các câu trả lời (1)

Hi,

This forum is intended to help users with Mozilla products, such as Firefox. Your question appears to be outside the scope of our support forum, so as a moderator, I’m going to lock the thread and mark it as off-topic. Please see Mozilla Support rules and guidelines for more information.