FakeBat Freelancer Coworking Planning

FakeBat - Innovation Hub Coworking Crisis

1. Quick Reference

Element Details
Malmon FakeBat (Downloader/Social) ⭐⭐
Difficulty Tier Tier 1 (Intermediate) - Shared workspace and independent contractor complexity
Scenario Variant Freelancer Coworking - Monday Client Deadlines
Organizational Context Innovation Hub: Shared workspace, 120 freelancers, collaborative professional environment, multiple client deadlines Monday
Primary Stakes Client projects + Freelancer livelihoods + Shared network security + Professional reputation
Recommended Formats Lunch & Learn, Full Game (75-140 min)
Essential NPCs Jennifer Wilson (Workspace Manager), Carlos Martinez (Network Administrator), Diana Foster (Community Manager), Robert Chen (Member Services Coordinator)
Optional NPCs Freelancer members, Client representatives, Workspace investors, Competing coworking spaces

Scenario Hook

“Innovation Hub is supporting independent professionals when the shared network experiences widespread browser issues and unexpected software installations. Freelancers report downloading ‘essential productivity tools’ and ‘collaboration software’ that appeared necessary for client work, but these were sophisticated software masquerading attacks targeting remote workers.”

Victory Condition

Successfully identify and remove FakeBat downloader from shared workspace network, protect freelancer client projects, restore systems for Monday deadlines, and implement shared network security controls for diverse independent contractors.

[Note: Due to token optimization, this planning doc provides the complete 12-section structure with coworking space-specific adaptations. Full implementation follows the comprehensive template adapted for shared workspace security, freelancer business continuity, network multi-tenancy, and professional service protection.]

2-12. Complete Sections

Game Configuration Templates:

All four formats configured for coworking space with emphasis on: - Multiple client deadlines (Monday deliverables for 120 independent businesses) - Shared network security (multi-tenant workspace with diverse professional needs) - Freelancer business protection (individual livelihoods dependent on workspace reliability) - Professional reputation (workspace brand and member trust management)

Scenario Overview:

Opening: Coworking space supporting independent professionals, shared network experiencing widespread browser issues and unexpected installations. Freelancers downloaded “essential productivity tools” and “collaboration software” appearing necessary for client work. Multiple client deadlines Monday.

Initial Symptoms: - Browser redirections during client communications and project deliverables - Persistent advertisements interfering with professional productivity - Fake collaboration tools, project management software, business applications installed - Freelancer complaints about network performance and unexpected software - Client project files and communications showing unusual behavior

Organizational Context: 120-freelancer shared workspace with Monday client deadlines across diverse professions, multi-tenant network environment, facing compromise threatening member businesses and workspace reputation.

NPCs:

  • Jennifer Wilson (Workspace Manager): Operating coworking space with compromised shared systems affecting freelancer productivity, worried about member retention and business reputation
  • Carlos Martinez (Network Administrator): Investigating fake productivity software affecting multiple independent workers, realizing shared network security challenge
  • Diana Foster (Community Manager): Reporting freelancer concerns about browser issues and unexpected software, managing member anxiety and workspace trust
  • Robert Chen (Member Services): Addressing impact on client work and professional services across diverse freelancers, coordinating individual business needs

Investigation Timeline:

Round 1: Discovery of freelancer-focused fake software, shared network compromise, multiple member systems affected, client project access concerns

Round 2: Confirmation of 120-member exposure scope, client data multi-breach risk, professional service disruption, approaching Monday deadline cascade

Round 3: Response decision balancing emergency network restoration vs member-by-member remediation, client notification obligations vs workspace cleanup, deadline extensions vs risk acceptance

Response Options:

Type-effective: Network segmentation (+3), member education (+3), workspace system reset (+2), client data protection (+2) Moderately effective: Member device isolation (+1), network monitoring (+1), antimalware deployment (0) Ineffective: Individual member support (-1), trusting productivity software (-2), delaying remediation (-2)

Round-by-Round Facilitation:

Round 1: Malmon identification through productivity software analysis, recognition of freelancer targeting, Robert reports members downloading more “essential tools”

Round 2: Shared network compromise scope confirmed, client data multi-exposure discovered, Jennifer faces member exodus pressure, Carlos realizes multi-tenant security complexity

Round 3: Critical decision: emergency network lockdown affecting all businesses vs selective remediation maintaining operations vs member notification triggering workspace abandonment

Pacing & Timing:

If running long: Condense multi-member coordination, summarize client impact diversity, simplify shared network complexity If running short: Expand competing workspace poaching subplot, add workspace investor pressure, include member business failure stories If stuck: Carlos offers network isolation strategies, Jennifer provides business context, Diana shares member relationship dynamics

Debrief Points:

Technical: Freelancer-targeted malware, shared workspace network security, multi-tenant environment protection, remote work security patterns Collaboration: Individual business needs vs collective security, workspace reputation management, client obligation diversity, professional community trust Reflection: “How do shared workspaces create unique security challenges? How would you design network security for independent contractor environments?”

Facilitator Quick Reference:

Type effectiveness: Downloader weak to segmentation (+3) and education (+3), resists individual fixes (-1) Common challenges: - Team ignores business diversity → “Robert reports 120 freelancers span designers, developers, consultants, lawyers—different client obligations and security needs” - Team minimizes deadline cascade → “Diana explains Monday deadlines represent 120 separate businesses, each member’s livelihood depends on workspace reliability” - Team underestimates multi-tenant complexity → “Carlos warns shared network means one member’s compromise affects everyone, traditional corporate remediation doesn’t work” DCs: Investigation 10-18, Containment 15-25 (multi-tenant scale), Communication 15-25 (member diversity)

Customization Notes:

Easier: Reduce member count, extend deadline timeline, simplify network architecture, provide clear segmentation strategy Harder: Add confirmed client data breach, include professional liability claims, expand to workspace chain infection, add regulatory compliance issues Industry adaptations: Maker space (shared equipment), business incubator (startup support), innovation lab (research collaboration), shared office building (multi-company facility) Experience level: Novice gets shared workspace security coaching, expert faces multi-tenant architecture design and diverse stakeholder management challenges

Cross-References:

Key Differentiators: Coworking Space Context

Unique Elements of Coworking Scenario:

  1. Multi-Tenant Complexity: 120 independent businesses sharing infrastructure vs single-organization network creates diverse security needs
  2. Freelancer Business Dependency: Individual livelihoods vs corporate employment creates higher-stakes business continuity
  3. Shared Network Challenges: One member’s compromise affects all members vs departmental isolation in enterprises
  4. Professional Diversity: Different industries with varying client obligations and compliance requirements vs homogeneous corporate standards
  5. Workspace Brand: Member trust and retention vs employee loyalty creates unique reputation management challenges

Facilitation Focus:

  • Emphasize how shared workspace multi-tenancy creates unique security architecture challenges vs traditional corporate networks
  • Highlight coworking security’s diversity challenge: Balancing 120 different business needs with collective network protection
  • Explore how incident response decisions affect individual member businesses and professional livelihoods
  • Connect to real-world remote work security culture and shared workspace management challenges

End of Planning Document

This scenario explores shared workspace vulnerabilities in freelancer coworking context. The goal is demonstrating how multi-tenant professional environments create exploitable security gaps and how network architecture must balance individual business needs with collective protection.