Company Details
major-league-baseball
34,514
429,879
7112
mlb.com
0
MAJ_9807813
In-progress

Major League Baseball (MLB) Company CyberSecurity Posture
mlb.comMajor League Baseball (MLB) is the most historic professional sports league in the United States and consists of 30 member clubs in the U.S. and Canada, representing the highest level of professional baseball. Led by Commissioner Robert D. Manfred, Jr., MLB remains committed to making an impact in the communities of the U.S., Canada and throughout the world, perpetuating the sport's larger role in society and permeating every facet of baseball's business, marketing, community relations and social responsibility endeavors. MLB currently features record levels of competitive balance, continues to expand its global reach through programming and content to fans all over the world, and registered records in games and minutes watched this season on MLB.TV. With the continued success of MLB Network and MLB digital platforms, MLB continues to find innovative ways for its fans to enjoy America's National Pastime and a truly global game. For more information on Major League Baseball, visit www.MLB.com.
Company Details
major-league-baseball
34,514
429,879
7112
mlb.com
0
MAJ_9807813
In-progress
Between 650 and 699

MLB Global Score (TPRM)XXXX

Description: The MLB's facial recognition program, referred to as Go-Ahead Entry, has raised privacy and security concerns among fans and privacy advocates. The program allows for expedited entry into the stadiums for fans who opt-in by submitting a selfie via an app, enabling their faces to be matched at camera kiosks. While the technology is intended to enhance the event experience by reducing wait times, critics argue that it may contribute to increased surveillance and data security risks, despite assurances from the facial recognition company Wicket regarding data privacy and responsible use. The use of facial recognition is contentious, with potential for misuse or data breaches, prompting protests and skepticism about such systems' security measures.
Description: The MLB Ballpark app, used by fans to store and manage game tickets, was targeted by bad actors exploiting leaked or stolen credentials from other breaches. Hackers accessed fan accounts, stole coveted MLB tickets, and forwarded them to unauthorized accounts for resale on third-party platforms. Victims included a Philadelphia fan who lost seven bachelor party tickets, later finding strangers occupying their seats, and an Illinois man who missed the first hour of a Cubs game due to vanished tickets. While MLB confirmed no breach of its own systems, the incident disrupted stadium entry for many, eroded customer trust, and highlighted vulnerabilities in digital ticketing platforms. Fraudsters capitalized on weak password hygiene and the high liquidity of live-event tickets, accelerating account takeovers. MLB responded with security updates, but the exploit underscored broader risks in the $12.5B+ fraud landscape, where credential stuffing and automated resale bots increasingly target high-demand markets. The league’s proprietary app—praised for features like facial recognition—ironically became a vector for fraud due to its seamless ticket-sharing functionality.


Major League Baseball (MLB) has 25.0% more incidents than the average of same-industry companies with at least one recorded incident.
Major League Baseball (MLB) has 56.25% more incidents than the average of all companies with at least one recorded incident.
Major League Baseball (MLB) reported 1 incidents this year: 0 cyber attacks, 0 ransomware, 0 vulnerabilities, 1 data breaches, compared to industry peers with at least 1 incident.
MLB cyber incidents detection timeline including parent company and subsidiaries

Major League Baseball (MLB) is the most historic professional sports league in the United States and consists of 30 member clubs in the U.S. and Canada, representing the highest level of professional baseball. Led by Commissioner Robert D. Manfred, Jr., MLB remains committed to making an impact in the communities of the U.S., Canada and throughout the world, perpetuating the sport's larger role in society and permeating every facet of baseball's business, marketing, community relations and social responsibility endeavors. MLB currently features record levels of competitive balance, continues to expand its global reach through programming and content to fans all over the world, and registered records in games and minutes watched this season on MLB.TV. With the continued success of MLB Network and MLB digital platforms, MLB continues to find innovative ways for its fans to enjoy America's National Pastime and a truly global game. For more information on Major League Baseball, visit www.MLB.com.


The National Basketball Association (NBA) is a global sports and media organization with the mission to inspire and connect people everywhere through the power of basketball. Built around five professional sports leagues: the NBA, WNBA, NBA G League, NBA 2K League and Basketball Africa League, the
.png)
MLB officially announced new media rights deals with NBC, Netflix and ESPN until 2028.
MLB News: Toronto Blue Jays pitcher Trey Yesavage, a 22-year-old phenom, is rapidly ascending in Major League Baseball.
Shohei Ohtani is driving incredible sponsorship revenues for the Dodgers, helping push MLB past $2 billion in team sponsors for the first...
The Toronto Blue Jays are the only Canadian-based Major League Baseball team to win the World Series but their last title was in 1993.
As the playoffs approach, Major League Baseball is dealing with a flurry of online ticket thefts tied to its Ballpark app.
ATLANTA — The 2025 Major League Baseball (MLB) All-Star game brought thousands of fans, players, and members of the media from around the...
Major League Baseball's (MLB) long-term vision for prosperity begins with expansion and realignment. The aspiration is to add two new...
Rob Manfred has not said explicitly that the owners are seeking a salary cap in Major League Baseball, but the signs are there.
Major League Baseball is nearing a finalized agreement with Disney's ESPN, Comcast's NBC Sports and Netflix on new three-year media rights...

Explore insights on cybersecurity incidents, risk posture, and Rankiteo's assessments.
The official website of Major League Baseball (MLB) is http://www.mlb.com.
According to Rankiteo, Major League Baseball (MLB)’s AI-generated cybersecurity score is 652, reflecting their Weak security posture.
According to Rankiteo, Major League Baseball (MLB) currently holds 0 security badges, indicating that no recognized compliance certifications are currently verified for the organization.
According to Rankiteo, Major League Baseball (MLB) is not certified under SOC 2 Type 1.
According to Rankiteo, Major League Baseball (MLB) does not hold a SOC 2 Type 2 certification.
According to Rankiteo, Major League Baseball (MLB) is not listed as GDPR compliant.
According to Rankiteo, Major League Baseball (MLB) does not currently maintain PCI DSS compliance.
According to Rankiteo, Major League Baseball (MLB) is not compliant with HIPAA regulations.
According to Rankiteo,Major League Baseball (MLB) is not certified under ISO 27001, indicating the absence of a formally recognized information security management framework.
Major League Baseball (MLB) operates primarily in the Spectator Sports industry.
Major League Baseball (MLB) employs approximately 34,514 people worldwide.
Major League Baseball (MLB) presently has no subsidiaries across any sectors.
Major League Baseball (MLB)’s official LinkedIn profile has approximately 429,879 followers.
Major League Baseball (MLB) is classified under the NAICS code 7112, which corresponds to Spectator Sports.
No, Major League Baseball (MLB) does not have a profile on Crunchbase.
Yes, Major League Baseball (MLB) maintains an official LinkedIn profile, which is actively utilized for branding and talent engagement, which can be accessed here: https://www.linkedin.com/company/major-league-baseball.
As of November 27, 2025, Rankiteo reports that Major League Baseball (MLB) has experienced 2 cybersecurity incidents.
Major League Baseball (MLB) has an estimated 6,358 peer or competitor companies worldwide.
Incident Types: The types of cybersecurity incidents that have occurred include Breach.
Total Financial Loss: The total financial loss from these incidents is estimated to be $100 million.
Detection and Response: The company detects and responds to cybersecurity incidents through an incident response plan activated with yes (mlb issued public statements and implemented security updates), and containment measures with account lockouts, containment measures with password reset enforcement, containment measures with security patch deployment, and remediation measures with enhanced authentication prompts, remediation measures with fraud monitoring, remediation measures with user education on password hygiene, and recovery measures with ticket replacement for affected fans, recovery measures with customer support escalation, and communication strategy with public apology, communication strategy with media statements, communication strategy with in-app notifications for password updates, and enhanced monitoring with yes (fraud detection for ticket transfers)..
Title: MLB Facial Recognition Program Privacy Concerns
Description: The MLB's facial recognition program, referred to as Go-Ahead Entry, has raised privacy and security concerns among fans and privacy advocates. The program allows for expedited entry into the stadiums for fans who opt-in by submitting a selfie via an app, enabling their faces to be matched at camera kiosks. While the technology is intended to enhance the event experience by reducing wait times, critics argue that it may contribute to increased surveillance and data security risks, despite assurances from the facial recognition company Wicket regarding data privacy and responsible use. The use of facial recognition is contentious, with potential for misuse or data breaches, prompting protests and skepticism about such systems' security measures.
Type: Privacy and Security Concerns
Title: MLB Ballpark App Account Takeover and Ticket Theft Incident
Description: Baseball fans across multiple U.S. cities experienced unauthorized access to their MLB Ballpark app accounts, resulting in stolen or disappeared game tickets. The incident was attributed to 'bad actors' using leaked or stolen credentials from other breaches to access fan accounts. While MLB systems were not directly compromised, the app's ticket-sharing functionality was exploited to forward tickets to unauthorized third-party accounts, likely for resale. The issue spiked in early September 2024, prompting MLB to implement security updates and mitigate the fraud. Multiple fans reported disruptions, including denied stadium entry and financial losses, with at least one legal complaint filed in Illinois.
Date Detected: 2024-09-01T00:00:00Z
Date Publicly Disclosed: 2024-09-12T00:00:00Z
Type: Account Takeover (ATO)
Attack Vector: Stolen/Leaked CredentialsWeak/Reused PasswordsExploited Ticket-Sharing Functionality
Vulnerability Exploited: Lack of Multi-Factor Authentication (MFA) EnforcementWeak Password PoliciesOver-Permissive Ticket Transfer Features
Threat Actor: Opportunistic CybercriminalsAccount Takeover (ATO) Groups
Motivation: Financial GainTicket Resale ProfitExploitation of Secondary Market Demand
Common Attack Types: The most common types of attacks the company has faced is Breach.
Identification of Attack Vectors: The company identifies the attack vectors used in incidents through Credential Stuffing (using leaked passwords from other breaches).

Data Compromised: Facial recognition data, Selfies
Customer Complaints: ['Protests', 'Skepticism']

Financial Loss: Undisclosed (Individual cases include $100,000 in fraudulent 'Wicked' ticket purchases via stolen credit cards in a related incident; broader consumer fraud losses exceeded $12.5B in 2024 per FTC)
Data Compromised: Account credentials, Ticket ownership records, Payment information (in related incidents)
Systems Affected: MLB Ballpark App (iOS/Android)SeatGeek IntegrationTicket Transfer Functionality
Operational Impact: Disrupted Stadium EntryCustomer Support OverloadReputation Damage
Revenue Loss: ['Potential Loss from Ticket Resales', 'Customer Churn Risk', 'Litigation Costs']
Customer Complaints: ['Widespread (Reddit threads, legal complaints, fan reports across multiple cities)']
Brand Reputation Impact: High (Negative media coverage, erosion of trust in digital ticketing)
Legal Liabilities: Ongoing Litigation (Illinois legal complaint filed)
Identity Theft Risk: ['Moderate (Reused credentials from other breaches)']
Payment Information Risk: ['Low-Moderate (No direct breach of MLB systems, but related incidents involved stolen credit cards)']
Average Financial Loss: The average financial loss per incident is $50.00 million.
Commonly Compromised Data Types: The types of data most commonly compromised in incidents are Facial Recognition Data, Selfies, , Account Credentials (From External Breaches), Ticket Ownership Data and .

Entity Name: Major League Baseball (MLB)
Entity Type: Sports Organization
Industry: Sports and Entertainment

Entity Name: Major League Baseball (MLB)
Entity Type: Sports League
Industry: Entertainment/Sports
Location: United States (Nationwide)
Size: Large (30 teams, millions of fans)
Customers Affected: Thousands (Exact number undisclosed; widespread reports from Los Angeles, Detroit, Miami, Boston, Philadelphia, Chicago)

Entity Name: MLB Ballpark App Users
Entity Type: Consumers
Location: United States (Multiple Cities)
Customers Affected: Thousands

Incident Response Plan Activated: Yes (MLB issued public statements and implemented security updates)
Containment Measures: Account LockoutsPassword Reset EnforcementSecurity Patch Deployment
Remediation Measures: Enhanced Authentication PromptsFraud MonitoringUser Education on Password Hygiene
Recovery Measures: Ticket Replacement for Affected FansCustomer Support Escalation
Communication Strategy: Public ApologyMedia StatementsIn-App Notifications for Password Updates
Enhanced Monitoring: Yes (Fraud detection for ticket transfers)
Incident Response Plan: The company's incident response plan is described as Yes (MLB issued public statements and implemented security updates).

Type of Data Compromised: Facial recognition data, Selfies

Type of Data Compromised: Account credentials (from external breaches), Ticket ownership data
Sensitivity of Data: Moderate (Ticket access, potential PII if linked to payment methods)
Data Exfiltration: Yes (Tickets forwarded to unauthorized accounts)
Personally Identifiable Information: Potential (if accounts linked to payment/personal details)
Prevention of Data Exfiltration: The company takes the following measures to prevent data exfiltration: Enhanced Authentication Prompts, Fraud Monitoring, User Education on Password Hygiene, .
Handling of PII Incidents: The company handles incidents involving personally identifiable information (PII) through by account lockouts, password reset enforcement, security patch deployment and .
Data Recovery from Ransomware: The company recovers data encrypted by ransomware through Ticket Replacement for Affected Fans, Customer Support Escalation, .

Legal Actions: Pending (Illinois legal complaint filed),
Ensuring Regulatory Compliance: The company ensures compliance with regulatory requirements through Pending (Illinois legal complaint filed), .

Lessons Learned: Credential stuffing remains a pervasive threat, especially for apps handling high-value assets like event tickets., Convenience features (e.g., 'effortless ticket sharing') can become attack vectors if not secured with MFA or rate limits., Consumer password hygiene continues to lag, necessitating proactive measures like enforced MFA or password managers., Secondary markets for tickets create incentives for fraud, requiring real-time fraud detection in transfer functionalities.

Recommendations: Enforce multi-factor authentication (MFA) for all account actions, especially ticket transfers., Implement behavioral analytics to detect anomalous ticket-sharing patterns (e.g., rapid transfers to new accounts)., Partner with identity verification services to flag credentials known to be compromised in other breaches., Educate users on password hygiene and risks of credential reuse via in-app prompts and email campaigns., Audit and restrict ticket-transfer functionalities to prevent bulk or suspicious forwards., Monitor dark web forums for stolen MLB-related credentials or fraud tutorials targeting the app., Consider rate-limiting ticket transfers or requiring additional verification for high-value transactions.Enforce multi-factor authentication (MFA) for all account actions, especially ticket transfers., Implement behavioral analytics to detect anomalous ticket-sharing patterns (e.g., rapid transfers to new accounts)., Partner with identity verification services to flag credentials known to be compromised in other breaches., Educate users on password hygiene and risks of credential reuse via in-app prompts and email campaigns., Audit and restrict ticket-transfer functionalities to prevent bulk or suspicious forwards., Monitor dark web forums for stolen MLB-related credentials or fraud tutorials targeting the app., Consider rate-limiting ticket transfers or requiring additional verification for high-value transactions.Enforce multi-factor authentication (MFA) for all account actions, especially ticket transfers., Implement behavioral analytics to detect anomalous ticket-sharing patterns (e.g., rapid transfers to new accounts)., Partner with identity verification services to flag credentials known to be compromised in other breaches., Educate users on password hygiene and risks of credential reuse via in-app prompts and email campaigns., Audit and restrict ticket-transfer functionalities to prevent bulk or suspicious forwards., Monitor dark web forums for stolen MLB-related credentials or fraud tutorials targeting the app., Consider rate-limiting ticket transfers or requiring additional verification for high-value transactions.Enforce multi-factor authentication (MFA) for all account actions, especially ticket transfers., Implement behavioral analytics to detect anomalous ticket-sharing patterns (e.g., rapid transfers to new accounts)., Partner with identity verification services to flag credentials known to be compromised in other breaches., Educate users on password hygiene and risks of credential reuse via in-app prompts and email campaigns., Audit and restrict ticket-transfer functionalities to prevent bulk or suspicious forwards., Monitor dark web forums for stolen MLB-related credentials or fraud tutorials targeting the app., Consider rate-limiting ticket transfers or requiring additional verification for high-value transactions.Enforce multi-factor authentication (MFA) for all account actions, especially ticket transfers., Implement behavioral analytics to detect anomalous ticket-sharing patterns (e.g., rapid transfers to new accounts)., Partner with identity verification services to flag credentials known to be compromised in other breaches., Educate users on password hygiene and risks of credential reuse via in-app prompts and email campaigns., Audit and restrict ticket-transfer functionalities to prevent bulk or suspicious forwards., Monitor dark web forums for stolen MLB-related credentials or fraud tutorials targeting the app., Consider rate-limiting ticket transfers or requiring additional verification for high-value transactions.Enforce multi-factor authentication (MFA) for all account actions, especially ticket transfers., Implement behavioral analytics to detect anomalous ticket-sharing patterns (e.g., rapid transfers to new accounts)., Partner with identity verification services to flag credentials known to be compromised in other breaches., Educate users on password hygiene and risks of credential reuse via in-app prompts and email campaigns., Audit and restrict ticket-transfer functionalities to prevent bulk or suspicious forwards., Monitor dark web forums for stolen MLB-related credentials or fraud tutorials targeting the app., Consider rate-limiting ticket transfers or requiring additional verification for high-value transactions.Enforce multi-factor authentication (MFA) for all account actions, especially ticket transfers., Implement behavioral analytics to detect anomalous ticket-sharing patterns (e.g., rapid transfers to new accounts)., Partner with identity verification services to flag credentials known to be compromised in other breaches., Educate users on password hygiene and risks of credential reuse via in-app prompts and email campaigns., Audit and restrict ticket-transfer functionalities to prevent bulk or suspicious forwards., Monitor dark web forums for stolen MLB-related credentials or fraud tutorials targeting the app., Consider rate-limiting ticket transfers or requiring additional verification for high-value transactions.
Key Lessons Learned: The key lessons learned from past incidents are Credential stuffing remains a pervasive threat, especially for apps handling high-value assets like event tickets.,Convenience features (e.g., 'effortless ticket sharing') can become attack vectors if not secured with MFA or rate limits.,Consumer password hygiene continues to lag, necessitating proactive measures like enforced MFA or password managers.,Secondary markets for tickets create incentives for fraud, requiring real-time fraud detection in transfer functionalities.
Implemented Recommendations: The company has implemented the following recommendations to improve cybersecurity: Audit and restrict ticket-transfer functionalities to prevent bulk or suspicious forwards., Implement behavioral analytics to detect anomalous ticket-sharing patterns (e.g., rapid transfers to new accounts)., Consider rate-limiting ticket transfers or requiring additional verification for high-value transactions., Partner with identity verification services to flag credentials known to be compromised in other breaches., Monitor dark web forums for stolen MLB-related credentials or fraud tutorials targeting the app., Enforce multi-factor authentication (MFA) for all account actions, especially ticket transfers. and Educate users on password hygiene and risks of credential reuse via in-app prompts and email campaigns..

Source: Sportico
URL: https://www.sportico.com/leagues/baseball/2024/mlb-ballpark-app-ticket-theft-12346789
Date Accessed: 2024-09-15

Source: Reddit (r/baseball)
URL: https://www.reddit.com/r/baseball/comments/xyz123/mlb_ballpark_app_tickets_disappearing/
Date Accessed: 2024-09-14

Source: U.S. Federal Trade Commission (FTC) Report on Fraud Losses
Date Accessed: 2024-09-10

Source: Binary Defense Threat Report
URL: https://www.binarydefense.com/credential-stuffing-attacks-up-24-in-2024/
Date Accessed: 2024-09-05
Additional Resources: Stakeholders can find additional resources on cybersecurity best practices at and Source: SporticoUrl: https://www.sportico.com/leagues/baseball/2024/mlb-ballpark-app-ticket-theft-12346789Date Accessed: 2024-09-15, and Source: Reddit (r/baseball)Url: https://www.reddit.com/r/baseball/comments/xyz123/mlb_ballpark_app_tickets_disappearing/Date Accessed: 2024-09-14, and Source: U.S. Federal Trade Commission (FTC) Report on Fraud LossesUrl: https://www.ftc.gov/news-events/news/press-releases/2024/02/new-ftc-data-show-consumers-reported-losing-more-10-billion-fraud-2023Date Accessed: 2024-09-10, and Source: Binary Defense Threat ReportUrl: https://www.binarydefense.com/credential-stuffing-attacks-up-24-in-2024/Date Accessed: 2024-09-05.

Investigation Status: Ongoing (MLB mitigating issue; litigation pending)
Communication of Investigation Status: The company communicates the status of incident investigations to stakeholders through Public Apology, Media Statements and In-App Notifications For Password Updates.

Stakeholder Advisories: Mlb Urged Fans To Update Passwords And Enable Mfa Where Available..
Customer Advisories: In-app notifications and email alerts sent to users about account security.
Advisories Provided: The company provides the following advisories to stakeholders and customers following an incident: were Mlb Urged Fans To Update Passwords And Enable Mfa Where Available., In-App Notifications And Email Alerts Sent To Users About Account Security. and .

Entry Point: Credential Stuffing (using leaked passwords from other breaches)
Reconnaissance Period: Unknown (Likely ongoing; exploit accelerated in early September 2024)
High Value Targets: Mlb Ballpark App Accounts With Active Tickets, Accounts Linked To Payment Methods,
Data Sold on Dark Web: Mlb Ballpark App Accounts With Active Tickets, Accounts Linked To Payment Methods,

Root Causes: Lack Of Enforced Mfa For Ticket Transfers., Over-Reliance On User Password Hygiene (Many Reused Credentials From Other Breaches)., Excessively Permissive Ticket-Sharing Functionality Without Fraud Controls., Delayed Detection Of Anomalous Transfer Patterns.,
Corrective Actions: Deployed Security Patches To Restrict Unauthorized Transfers., Enhanced Monitoring For Credential Stuffing Attempts., Public Campaign To Promote Password Updates And Mfa Adoption., Legal Review Of Data Security Obligations (Per Illinois Complaint).,
Post-Incident Analysis Process: The company's process for conducting post-incident analysis is described as Yes (Fraud detection for ticket transfers).
Corrective Actions Taken: The company has taken the following corrective actions based on post-incident analysis: Deployed Security Patches To Restrict Unauthorized Transfers., Enhanced Monitoring For Credential Stuffing Attempts., Public Campaign To Promote Password Updates And Mfa Adoption., Legal Review Of Data Security Obligations (Per Illinois Complaint)., .
Last Attacking Group: The attacking group in the last incident was an Opportunistic CybercriminalsAccount Takeover (ATO) Groups.
Most Recent Incident Detected: The most recent incident detected was on 2024-09-01T00:00:00Z.
Most Recent Incident Publicly Disclosed: The most recent incident publicly disclosed was on 2024-09-12T00:00:00Z.
Highest Financial Loss: The highest financial loss from an incident was Undisclosed (Individual cases include $100,000 in fraudulent 'Wicked' ticket purchases via stolen credit cards in a related incident; broader consumer fraud losses exceeded $12.5B in 2024 per FTC).
Most Significant Data Compromised: The most significant data compromised in an incident were Facial recognition data, Selfies, , Account Credentials, Ticket Ownership Records, Payment Information (in related incidents) and .
Most Significant System Affected: The most significant system affected in an incident was MLB Ballpark App (iOS/Android)SeatGeek IntegrationTicket Transfer Functionality.
Containment Measures in Most Recent Incident: The containment measures taken in the most recent incident was Account LockoutsPassword Reset EnforcementSecurity Patch Deployment.
Most Sensitive Data Compromised: The most sensitive data compromised in a breach were Facial recognition data, Account Credentials, Ticket Ownership Records, Selfies and Payment Information (in related incidents).
Most Significant Legal Action: The most significant legal action taken for a regulatory violation was Pending (Illinois legal complaint filed), .
Most Significant Lesson Learned: The most significant lesson learned from past incidents was Secondary markets for tickets create incentives for fraud, requiring real-time fraud detection in transfer functionalities.
Most Significant Recommendation Implemented: The most significant recommendation implemented to improve cybersecurity was Audit and restrict ticket-transfer functionalities to prevent bulk or suspicious forwards., Implement behavioral analytics to detect anomalous ticket-sharing patterns (e.g., rapid transfers to new accounts)., Consider rate-limiting ticket transfers or requiring additional verification for high-value transactions., Partner with identity verification services to flag credentials known to be compromised in other breaches., Monitor dark web forums for stolen MLB-related credentials or fraud tutorials targeting the app., Enforce multi-factor authentication (MFA) for all account actions, especially ticket transfers. and Educate users on password hygiene and risks of credential reuse via in-app prompts and email campaigns..
Most Recent Source: The most recent source of information about an incident are Reddit (r/baseball), Binary Defense Threat Report, Sportico and U.S. Federal Trade Commission (FTC) Report on Fraud Losses.
Most Recent URL for Additional Resources: The most recent URL for additional resources on cybersecurity best practices is https://www.sportico.com/leagues/baseball/2024/mlb-ballpark-app-ticket-theft-12346789, https://www.reddit.com/r/baseball/comments/xyz123/mlb_ballpark_app_tickets_disappearing/, https://www.ftc.gov/news-events/news/press-releases/2024/02/new-ftc-data-show-consumers-reported-losing-more-10-billion-fraud-2023, https://www.binarydefense.com/credential-stuffing-attacks-up-24-in-2024/ .
Current Status of Most Recent Investigation: The current status of the most recent investigation is Ongoing (MLB mitigating issue; litigation pending).
Most Recent Stakeholder Advisory: The most recent stakeholder advisory issued was MLB urged fans to update passwords and enable MFA where available., .
Most Recent Customer Advisory: The most recent customer advisory issued was an In-app notifications and email alerts sent to users about account security.
Most Recent Entry Point: The most recent entry point used by an initial access broker was an Credential Stuffing (using leaked passwords from other breaches).
Most Recent Reconnaissance Period: The most recent reconnaissance period for an incident was Unknown (Likely ongoing; exploit accelerated in early September 2024).
.png)
Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to versions 19.2.16, 20.3.14, and 21.0.1, there is a XSRF token leakage via protocol-relative URLs in angular HTTP clients. The vulnerability is a Credential Leak by App Logic that leads to the unauthorized disclosure of the Cross-Site Request Forgery (XSRF) token to an attacker-controlled domain. Angular's HttpClient has a built-in XSRF protection mechanism that works by checking if a request URL starts with a protocol (http:// or https://) to determine if it is cross-origin. If the URL starts with protocol-relative URL (//), it is incorrectly treated as a same-origin request, and the XSRF token is automatically added to the X-XSRF-TOKEN header. This issue has been patched in versions 19.2.16, 20.3.14, and 21.0.1. A workaround for this issue involves avoiding using protocol-relative URLs (URLs starting with //) in HttpClient requests. All backend communication URLs should be hardcoded as relative paths (starting with a single /) or fully qualified, trusted absolute URLs.
Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. An Uncontrolled Recursion vulnerability in node-forge versions 1.3.1 and below enables remote, unauthenticated attackers to craft deep ASN.1 structures that trigger unbounded recursive parsing. This leads to a Denial-of-Service (DoS) via stack exhaustion when parsing untrusted DER inputs. This issue has been patched in version 1.3.2.
Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. An Integer Overflow vulnerability in node-forge versions 1.3.1 and below enables remote, unauthenticated attackers to craft ASN.1 structures containing OIDs with oversized arcs. These arcs may be decoded as smaller, trusted OIDs due to 32-bit bitwise truncation, enabling the bypass of downstream OID-based security decisions. This issue has been patched in version 1.3.2.
Suricata is a network IDS, IPS and NSM engine developed by the OISF (Open Information Security Foundation) and the Suricata community. Prior to versions 7.0.13 and 8.0.2, working with large buffers in Lua scripts can lead to a stack overflow. Users of Lua rules and output scripts may be affected when working with large buffers. This includes a rule passing a large buffer to a Lua script. This issue has been patched in versions 7.0.13 and 8.0.2. A workaround for this issue involves disabling Lua rules and output scripts, or making sure limits, such as stream.depth.reassembly and HTTP response body limits (response-body-limit), are set to less than half the stack size.
Suricata is a network IDS, IPS and NSM engine developed by the OISF (Open Information Security Foundation) and the Suricata community. In versions from 8.0.0 to before 8.0.2, a NULL dereference can occur when the entropy keyword is used in conjunction with base64_data. This issue has been patched in version 8.0.2. A workaround involves disabling rules that use entropy in conjunction with base64_data.

Get company history
Every week, Rankiteo analyzes billions of signals to give organizations a sharper, faster view of emerging risks. With deeper, more actionable intelligence at their fingertips, security teams can outpace threat actors, respond instantly to Zero-Day attacks, and dramatically shrink their risk exposure window.
Identify exposed access points, detect misconfigured SSL certificates, and uncover vulnerabilities across the network infrastructure.
Gain visibility into the software components used within an organization to detect vulnerabilities, manage risk, and ensure supply chain security.
Monitor and manage all IT assets and their configurations to ensure accurate, real-time visibility across the company's technology environment.
Leverage real-time insights on active threats, malware campaigns, and emerging vulnerabilities to proactively defend against evolving cyberattacks.