Electronic Arts has quietly signaled a strategic shift that could reshape how its multiplayer games run on the next generation of mobile and laptop hardware: the company is actively recruiting a senior engineer to build a native ARM64 kernel driver for
EA Javelin Anticheat, explicitly to enable
Windows-on-Arm support and to begin laying groundwork for broader
Linux/Proton compatibility. The job listing makes clear that EA intends to port Javelin’s kernel-level protections to ARM hardware, implement hardware-aware loading of different anticheat binaries, and create automated build-and-test pipelines for validating Javelin on ARM devices. If executed, this work would remove one of the largest technical blockers preventing titles protected by Javelin from running natively (or reliably under translation layers) on ARM-based Windows machines and potentially on Linux-based Proton implementations — a move with meaningful technical, commercial, and privacy ramifications for gamers and platform makers alike.
Background: why this matters now
Windows-on-Arm is no longer an experiment. Over the last two years mobile and laptop silicon makers have shipped increasingly powerful ARM-based chips for consumer PCs, and manufacturers are building laptops and handhelds on that architecture that can deliver competitive performance with dramatically better battery life. At the same time, game developers and middleware vendors are racing to close a persistent compatibility gap: many PC games — especially multiplayer titles — rely on third-party anticheat systems that were originally written for x86_64 Windows and therefore either fail on or intentionally block ARM and Linux environments.
EA’s anticheat, rebranded as
EA Javelin Anticheat, is EA’s in-house, kernel-level system that runs at the deepest layer of the operating system to detect and block cheats that operate in ring 0. The company has emphasized Javelin’s impact: hundreds of specific detections, a 99%-plus accuracy rate on enforcement actions, and tens of millions of cheat attempts blocked across billions of sessions. But Javelin’s kernel-level design, combined with hardware and platform assumptions, has created a hard compatibility boundary that has excluded many ARM and Linux users from EA’s multiplayer ecosystem.
The new job advertisement from EA’s security organization explicitly tasks the hire with delivering a native ARM64 driver and with charting a path toward Linux and Proton. That single posting is the clearest public evidence yet that EA is preparing Javelin to work on Windows-on-Arm devices — and that the company is thinking beyond Windows to the realities of emulation and Proton-based compatibility layers.
What the job listing actually says (and what it implies)
The job posting spells out the responsibilities and technical expectations for the role in frank detail:
- Develop a native ARM driver for EA Javelin Anticheat, porting existing functionality to ARM.
- Support loading different versions of EA Javelin Anticheat based on user hardware, indicating multi-architecture support and runtime detection/dispatch.
- Implement build and test pipelines for automated validation of EA Javelin Anticheat on ARM hardware, which implies EA will invest in CI/CD across ARM test hardware.
- Design and solve for emerging security threats on ARM devices and chart a path for future OS/hardware support such as Linux and Proton.
Read together, these points imply several key objectives: deliver parity of detection capabilities on ARM, maintain safe and auditable behavior while running at kernel level, and prepare Javelin to be used in environments where games run through compatibility layers rather than natively compiled ARM binaries.
Why is that important? Because today, kernel-level anticheat systems are often the gating factor that prevents games from running on non-Windows configurations or under translation layers. If EA succeeds, it could remove or reduce that barrier for a subset of players — but not without new technical trade-offs.
The technical challenge: porting a kernel-level anticheat
Porting a kernel-level anticheat from x86_64 to ARM64 is not a simple compile-and-go task. The job requires domain expertise in Windows internals, low-level programming, drivers, compiler toolchains, and CPU intrinsics. Below are the core technical hurdles EA’s team will face:
- ABI and instruction-set differences: ARM64 and x86_64 differ in calling conventions, exception handling, and CPU features. Kernel-mode code that depends on x86-specific mechanisms must be rethought, not merely recompiled.
- Driver frameworks and signing: Windows drivers must conform to Microsoft’s kernel driver model and signing requirements. On modern Windows versions, driver signing (and Secure Boot interactions) can block unsigned or improperly signed drivers.
- Secure Boot and platform attestation: Several kernel-level anticheat systems (including Javelin in some deployments) check Secure Boot state or depend on Secure Boot being enabled. This creates compatibility roadblocks for Proton, custom Linux boot flows, and some handhelds.
- Hardware-accelerated features and intrinsics: Optimizations and low-level checks that rely on x86 instructions (e.g., performance counters, model-specific registers) require ARM equivalents or alternative approaches.
- Testing across ARM silicon variants: The ARM ecosystem includes many microarchitectural implementations; EA’s plan for automated validation pipelines is essential to ensure consistent behavior across vendors (Qualcomm, MediaTek, NVIDIA’s client silicon, and others).
- Interfacing with translation layers: If EA wants Javelin to work with Proton (which runs Windows binaries on Linux via translation), the anticheat must either:
- Run a native Linux/ARM kernel counterpart that can monitor the translated process, or
- Rely on the translation layer to present the right signals to a Windows-anticheat binary running under emulation — which is fraught with false positives and bypassable edge cases.
Each of these challenges demands careful engineering to preserve both security posture and system stability.
Windows-on-Arm, Proton, and the Steam Deck question
One of the loudest controversies around kernel-level anticheat is its impact on non-Windows platforms and emulators. Historically, the requirement to run a kernel-mode component has prevented many high-profile multiplayer games from functioning on the Steam Deck or other Linux-based systems. That situation has two vectors:
- Native Windows on Arm hardware (laptops and handhelds shipping with Windows) can, in principle, host a native ARM64 driver — if the anticheat exists for that architecture and passes driver-signing checks. A native driver on Windows-on-Arm would let titles protected by Javelin run without the translation pitfalls inherent to emulation.
- Linux and Proton pose a different problem. Proton runs Windows binaries on Linux by translating or recompiling instructions at runtime. For a kernel-level anticheat to function correctly under Proton, either the anticheat must run natively on Linux (in kernel mode) or the translation layer must reliably present the same runtime environment and system signals a Windows anticheat expects — an extremely brittle solution.
EA’s job posting explicitly references charting a path to Linux and Proton. That language suggests EA is thinking ahead about Proton-compatible anticheat or native Linux components. But that should be read as strategic planning, not a guarantee of broad cross-platform support.
Important caveat: other technical and policy constraints will still apply. Secure Boot checks, driver signing enforcement, and vendor-specific kernel interfaces might still prevent some devices (or some Proton workflows) from ever being fully compatible with Javelin — even if an ARM64 Windows driver exists.
Industry context: where Javelin sits among anticheat systems
EA Javelin is one of several kernel-level anticheat systems used by big publishers. The landscape includes:
- Vendor-built solutions like Riot’s Vanguard or Activision’s Ricochet, both of which run kernel components.
- Third-party services such as Easy Anti-Cheat (EAC) and BattlEye, which are widely used across the industry.
- Denuvo / other anti-tamper technologies, sometimes bundled with anticheat functionality.
Recently, one major development has been the move by some anticheat vendors to support ARM. Epic Games publicly added ARM support to
Easy Anti-Cheat, enabling EAC-protected titles to run on ARM-based Windows and Linux devices in certain configurations. That shift indicates market pressure: as ARM hardware becomes mainstream for laptops and handhelds, anticheat vendors must adapt or accept that large swathes of hardware will remain blocked.
EA building native ARM support for Javelin follows that trend. If multiple anticheat providers converge on ARM-compatible solutions, the result will be fewer artificial platform exclusions — but it may also normalize kernel-level system modules across more environments, raising the stakes around code quality, transparency, and auditing.
Security and privacy: kernel access is powerful — and risky
Kernel-mode components have the deepest privileges on a system. They can access memory and hardware that user-mode processes cannot, and that makes them uniquely powerful for both protective and malicious purposes.
EA has publicly argued that kernel-level operation is necessary to detect and block advanced cheats that operate in kernel space. The company stresses that Javelin only runs while protected games are active and that it limits telemetry to what is necessary. EA presents audit and assessment commitments to reassure players that the kernel driver will not be abused.
Still, there are real concerns to consider:
- Attack surface and bugs: Kernel drivers increase the system’s trusted computing base. Bugs in kernel modules can cause crashes, data corruption, or even privilege escalation vulnerabilities that attackers could exploit.
- Supply chain and updates: A driver that runs across millions of machines requires tight, auditable update mechanisms. If update channels are subverted or the driver signing process is compromised, attackers could push malicious code into kernel space.
- Transparency and third-party review: Even with internal audits, independent third-party code review and reproducible build practices reduce risk and increase trust. Industry best practice for kernel-mode components includes regular third-party audits, clear telemetry descriptions, and well-documented, minimal least-privilege designs.
- Platform control and vendor policies: Platforms enforce driver signing and boot-time policies (e.g., Secure Boot). These mechanisms protect users but also require anticheat providers to work closely with platform owners to avoid creating exclusionary lock-ins.
For users, the practical upshot is that kernel-level anticheat will remain a trade-off: stronger defenses against persistent, deeply embedded cheats versus broader system risk and higher barriers for alternative OSs and experimental setups.
Business drivers: why EA is making this move now
EA’s decision to hire for an ARM64 Javelin engineer is driven by a mix of technical necessity and commercial opportunity:
- Expanding market share: ARM-powered laptops and handhelds are growing in market share. Ensuring EA titles run properly on these devices protects potential revenue and reduces friction for new players.
- Ecosystem shifts: With major middleware vendors and platform holders (including Microsoft and Qualcomm) investing in ARM support, publishers have an incentive to follow suit to avoid ceding hardware segments to competitors.
- Retaining control over multiplayer integrity: Cheating undermines player retention and monetization models for live-service multiplayer titles. EA’s investment in Javelin’s portability seeks to lock in their capacity to enforce game integrity across platforms.
- Future-proofing against Proton and Linux growth: If Valve or other actors increase the share of gamers using Proton or Linux, the ability to support those environments — or at least to provide compatible anticheat — becomes commercially valuable.
From a corporate standpoint, enabling Javelin on ARM both defends EA’s existing player base and opens doors to new devices and regions where ARM PCs are prevalent.
What players should realistically expect
This is where speculation must be tempered with facts. The job posting is a clear signal of intent, but it is not a timetable or a guarantee of how quickly, or how broadly, support will appear in shipping games. Key takeaways for players and system builders:
- No immediate miracles: The job posting establishes a roadmap, not a release date. Developing, testing, and deploying a kernel-level driver across multiple ARM platforms and then integrating it into live games is a multi-step process that could take months or longer.
- Windows-on-Arm users are likeliest to benefit first: Native ARM64 drivers on Windows will be the most direct path to compatibility. If EA and partners ensure proper driver signing and Secure Boot compatibility, many Windows-on-Arm devices could see better support.
- Proton/Linux support is a more complex, longer-term goal: The posting’s mention of Linux and Proton is strategic. Actual Proton compatibility may require separate native Linux components, carefully designed interop, or alliance with platform providers. Expect that to be a multi-release, multi-year effort if pursued.
- Secure Boot, driver signing, and vendor policies will influence adoption: Even with a native ARM64 driver, vendor policies on driver signing or OEM customizations could prevent certain devices from running Javelin.
- Anticheat glitches remain possible: Kernel-level systems are complex. Users should expect teething problems — crashes, false positives, and conflicts with existing drivers are known issues historically with anticheat roll-outs.
Practical recommendations for WindowsForum readers
For enthusiasts, system builders, and gamers who follow Windows-on-Arm developments, here are practical steps to consider while EA’s work progresses:
- If you value Linux openness: Recognize that even if Proton compatibility improves, kernel-level anticheat may still force trade-offs. Decide whether playing protected EA titles is worth introducing kernel modules on your primary system.
- For Windows-on-Arm buyers: If EA games are important to you, watch for driver-signing and Secure Boot support in device specs. Prefer devices that support standard Windows driver workflows to minimize compatibility surprises.
- Backup before updates: Kernel driver installs and updates can be disruptive. Maintain backups and system restore points when installing early bleeding-edge drivers.
- Follow official patch notes: EA and its support channels typically publish troubleshooting guidance when anticheat updates roll out. Those notes often contain specific mitigation steps for conflicts with other software.
- Be cautious with third-party tweaks: Community workarounds that disable anticheat or circumvent driver checks can risk account bans and expose systems to malware.
- Advocate for auditability: If you’re active in the community, encourage EA and platform vendors to publish third-party audit results and to adopt transparent telemetry policies.
The broader platform and policy implications
As more publishers and middleware vendors move toward ARM support, several platform-level issues will require attention:
- Standardization of anticheat interfaces: The industry would benefit from clearer, standardized interfaces for legitimate anticheat needs that minimize kernel exposure where possible.
- Audit and governance frameworks: Independent security audits and public transparency reports should become the norm for kernel-level anticheat; players have a right to know what code runs with ring-0 privileges.
- Vendor coordination: Microsoft, Valve, and hardware vendors must cooperate with anticheat providers to define secure, user-protective pathways for driver signing, Secure Boot, and update mechanisms.
- User choice and opt-in policies: Platforms should consider clearer consent models and opt-in controls for high-privilege software, balanced with protections against cheating.
These are not trivial regulatory or technical shifts, but they will shape whether the next generation of anticheat solutions can be both effective and acceptable to broader user communities.
Strengths and risks: a balanced assessment
EA’s move to port Javelin to ARM64 carries clear benefits and serious risks.
Strengths
- Wider compatibility for players on ARM hardware: Native drivers on Windows-on-Arm could let more players access EA’s multiplayer titles without convoluted emulation workarounds.
- Stronger, consistent anti-cheat coverage across platforms: With Javelin on ARM, EA can maintain similar defensive capabilities across device classes, potentially improving fairness in competitive modes.
- Proactive engineering and automated validation: The job’s emphasis on pipelines and automated testing signals EA understands the complexity and is investing in infrastructure to reduce regressions.
Risks and concerns
- Increased system risk from kernel-level code: Expanding kernel-mode drivers to more systems heightens the consequences of bugs or supply-chain compromise.
- Privacy and transparency questions: Users rightly demand clarity about what data a kernel anticheat collects and how it is protected.
- Fragmentation and partial support: Even with an ARM64 driver, platform idiosyncrasies (OEMs, Secure Boot variants) will mean an uneven rollout and incomplete support across devices.
- Potential backlash from privacy- and freedom-oriented communities: The Linux and open-source gaming communities are likely to remain skeptical of kernel-mode anticheat, and any moves that appear to normalize deep kernel hooks will be controversial.
Conclusion: a pivotal but cautious milestone
EA’s recruitment for a Senior Anti-Cheat Engineer to build a native ARM64 Javelin driver is more than a job posting — it’s a clear strategic step toward making EA’s kernel-level protections compatible with the evolving hardware landscape. For gamers, platform vendors, and the broader industry, it marks a pivotal moment: anticheat vendors are finally taking ARM seriously, and major publishers see value in supporting the new class of devices.
That said, this is the beginning of a technical journey, not the finish line. The work ahead is deeply technical, legally and politically sensitive, and will require careful engineering, cooperation between platform holders and publishers, and transparent safeguards to preserve system stability and user privacy.
For anyone watching the intersection of Windows-on-Arm, Valve’s Proton ecosystem, and the continuing push to secure live-service multiplayer games, EA’s move is one to watch closely. It promises the possibility of broader access to EA’s multiplayer titles on ARM hardware — but only if the company balances anti-cheat efficacy with rigorous security practices and meaningful transparency about what their kernel code does and why.
The next few quarters will tell us whether EA’s technical ambitions translate into practical, well-vetted releases — and whether the industry can evolve anticheat design patterns in a way that respects both fair play and system integrity.
Source: TechPowerUp
EA Working on Javelin Anticheat Port for Windows-on-Arm | TechPowerUp}