Software Answers, a Banyan Software Listed by Pear Ransomware Group: Ransomware Claim — What’s Alleged & What To Do

On September 30, 2026, the ransomware and extortion group known as Pear listed Software Answers, a Banyan Software company, on its leak site. That listing is an accusation published by the group itself. It is not a confirmation from the company, a regulator, or an independent breach index. As of writing, Software Answers has not publicly confirmed that an incident occurred.

Leak-site postings have become a routine pressure tactic in today’s extortion landscape. Groups claim they hold stolen files and threaten publication to force payment. Some claims later prove accurate; others are inflated, recycled, or false. For customers, partners, and staff tied to long-term stay accommodation software, the practical question is not how dramatic the listing sounds, but what is actually established—and what sensible steps to take if personal or business data were ever involved.

What is being claimed

Pear has listed Software Answers, a Banyan Software, on its leak site. The public record supplied for this write-up does not describe how the group says access was obtained, what volume of material it claims to hold, or whether any deadline or sample files were posted. The number of people potentially affected is unknown. The types of data named as exposed are not disclosed in the available summary.

What is stated is that Software Answers is described as a software company serving the long-term stay accommodation industry, including corporate housing and serviced apartments. Beyond the fact of the listing and that sector description, timing of any alleged intrusion, technical method, and scale remain undisclosed in the material provided. The company has not, as of writing, publicly confirmed the incident.

A leak-site entry establishes that a group chose to name an organisation. It does not, by itself, prove that systems were compromised, that files left the environment, or that any particular dataset is in circulation. Readers should treat the listing as a claim until corroborated by the organisation or another authoritative source.

The group behind it: Pear

Pear operates in the same broad category as other ransomware and data-extortion crews: actors who seek leverage by claiming possession of internal data and by advertising victims on dedicated leak sites. In this model, publication—or the threat of it—is used to coerce payment. Listings are marketing as much as disclosure; groups often frame claims to maximise urgency.

Public reporting on such groups generally describes double-extortion patterns: encryption of systems in some cases, and separate pressure through alleged data theft even when encryption is not the main story. Specific tactics, toolsets, and prior victims vary by crew and over time. For this article, no claim by Pear about Software Answers is repeated beyond what the listing facts state. The group claims an association with this organisation by naming it; it has not, in the facts given here, provided a verified inventory of files or a confirmed victim count.

Because leak sites are controlled by the claimants, independent observers cannot treat their wording as an audit. Absence of technical detail in a listing is common and does not prove or disprove impact.

About Software Answers, a Banyan Software

Software Answers is identified as a Banyan Software company working in software for the long-term stay accommodation sector. That sector covers corporate housing, serviced apartments, and related stay products used by companies, relocation programmes, and travellers who need longer bookings than a typical hotel night.

Vendors in this space typically sit between property operators, corporate clients, and end guests. Their products may support reservations, billing, property operations, identity or stay records, and integrations with payment or HR-adjacent workflows. A listing that names such a vendor matters because the software often touches business contact data, stay and booking information, and operational records that several parties rely on—not only the software firm’s own employees.

Banyan Software is known publicly as a firm that acquires and holds vertical software businesses. Software Answers sits in that portfolio context as a specialised provider rather than a consumer social platform. The consequence of any genuine incident at a vendor like this would depend entirely on what systems and records were involved—an open question while the claim remains unconfirmed.

What was likely exposed

The facts do not name exposed data types. Exact contents are unconfirmed. It would be improper to state that any specific category of information was taken.

If files were taken from a software company serving corporate housing and serviced apartments, organisations in this sector typically hold some mix of the following—presented only as sector norms, not as an inventory of this claim:

• Business contact details for property operators, corporate clients, and partners
• Account, configuration, or support records tied to customer organisations
• Booking, stay, or guest-related operational data processed on behalf of clients, depending on product design
• Internal employee and contractor information, and routine corporate documents
• Technical materials such as source code, credentials stores, or infrastructure diagrams—only if those systems were in scope, which is unknown here

None of the above is established for this listing. People affected are unknown. Until Software Answers or a credible third party publishes a verified description, any discussion of “what may have been exposed” remains conditional.

The real-world impact

If the claim were accurate and data had left the organisation, risk would fall unevenly. Corporate clients might face targeted phishing that references real property, invoice, or stay details. Individuals whose names or contact data appear in vendor or guest systems could see more convincing fraud attempts. Property operators might worry about operational disruption or misuse of business records. The software company itself would face investigatory, contractual, and reputational work—again, only if an incident is real.

If the listing is exaggerated or false, the main near-term harm is uncertainty: customers and staff spend time checking posture, monitoring accounts, and seeking clarity that may not yet exist. That cost is real even when no data moved.

Nothing in the public facts supports a conclusion about how many people are involved, whether financial data was implicated, or whether any data has appeared outside the leak site. Impact assessments should stay proportionate to that uncertainty.

Steps worth taking either way

Because the incident is unconfirmed and data types are undisclosed, advice is precautionary. It is not a statement that your information is in this claim.

If you are a customer, partner, or employee connected to Software Answers or related long-term stay systems, consider routine hygiene: treat unexpected messages that cite bookings, invoices, or “breach follow-up” with scepticism; verify requests through known channels; watch financial and email accounts for unusual activity; and change passwords on related services if you reuse credentials elsewhere, preferably with unique passwords and multi-factor authentication.

Organisations that rely on the vendor can review contractual notice paths, confirm who is authorised to speak for the supplier, and ensure their own access to the product follows least privilege—without assuming the listing proves a compromise.

Readers who want a practical check can run a free exposure scan of their email address against known breach datasets. That kind of scan will not prove or disprove this specific Pear listing, but it can show whether the same address has already appeared in unrelated, previously recorded breaches and prompt tighter account security either way.

In short: Pear has listed Software Answers, a Banyan Software, on its leak site as of the September 30, 2026 report date; the company has not publicly confirmed an incident in the material available for this article; affected-person counts and data types remain unknown. Stay alert to conditional risk, demand primary confirmation before treating any detail as settled, and apply standard identity and account protections while the claim stays unverified.

AICompiled with AI assistance from public sources and published under our editorial standards.