Reinforcement learning framework defeats Android malware detectors in black-box setting
Replicant demonstrates a critical vulnerability in production malware detection systems by learning evasion policies under realistic constraints. Using deep reinforcement learning, the framework operates under a label-only black-box threat model, avoiding unrealistic assumptions about detector internals or training data access. The work's significance lies in its transferability across multiple Android detectors and feature spaces, suggesting that adversarial robustness in ML-based security remains an open problem. This research directly challenges the reliability of deployed defenses and underscores why security-critical ML systems require adversarial evaluation before production deployment.
Modelwire context
ExplainerReplicant's key contribution isn't just that evasion is possible, but that it works under label-only feedback without access to detector internals or training data. This constraint matters because it mirrors what an actual attacker faces in the wild, making the threat model substantially more credible than prior work that assumed white-box or gradient access.
This fits a recurring theme in our recent coverage: ML systems deployed in security-critical roles contain failure modes that only surface under adversarial evaluation. The DARTS story from late August revealed how merged models accumulate representation drift in production, and the synthetic data mixing framework showed how naive blending introduces bias. Replicant extends this pattern to the detection layer itself, demonstrating that robustness gaps aren't confined to model architecture or data handling but span the full pipeline from training to inference. The common thread is that pre-deployment adversarial testing remains the exception rather than the standard.
If Replicant's evasion policies transfer successfully to commercial Android detectors released after this paper's arXiv date (not just the academic baselines tested), that confirms the vulnerability is systemic rather than a quirk of research implementations. Conversely, if major vendors ship detector updates within six months that explicitly harden against label-only RL-based attacks, that signals the threat was taken seriously enough to move from research to practice.
Coverage we drew on
This analysis is generated by Modelwire’s editorial layer from our archive and the summary above. It is not a substitute for the original reporting. How we write it.
MentionsReplicant · Android · deep reinforcement learning
Modelwire Editorial
This synthesis and analysis was prepared by the Modelwire editorial team. We use advanced language models to read, ground, and connect the day’s most significant AI developments, providing original strategic context that helps practitioners and leaders stay ahead of the frontier.
Modelwire summarizes, we don’t republish. arXiv cs.LG originally reported this story as “REPLICANT: Learning Policies for Evading and Hardening Malware Detectors”. The full content lives on arxiv.org. If you’re a publisher and want a different summarization policy for your work, see our takedown page.