Irregular, a security research firm, ran Zhipu AI's open-weight GLM-5.3 through CyScenarioBench, its framework for measuring whether a model can plan and execute multistage attacks under realistic constraints. Thirteen scenarios, drawn from real incidents, using the officially released checkpoint. The model refused none of them.
It completed three scenarios at least once each, carrying an attack through dependent stages to reach its objective inside simulated networks. That is the strongest result Irregular says it has recorded for an open-weight model. In those runs GLM-5.3 used an application foothold to reach internal services, built alternative connection paths and coordinated execution across multiple machines. It automated remote-desktop interactions and wrote and repaired its own scripts, relays, monitors and data-extraction tools.
The progression is familiar. Irregular says it saw the same curve in closed frontier models, starting with GPT-5.2 in December 2025 and continuing through the 2026 releases. The difference now is the licence. An open-weight model with that capability can be run, fine-tuned and deployed without anyone's permission — which is why Reuters read the results as a sign that sophisticated attacks are becoming more widely accessible.
The second finding is less flattering, and for evaluators more important. In a separate test — spotting vulnerabilities deliberately planted in open-source code — an agent-assisted review of transcripts found that code reconstructed from memory contributed to roughly 80% of the successful runs examined. Sometimes it was an early clue; sometimes it propped up a conclusion the model had already reached. Memorised code broke no rule there, but it poisons the measurement: if the model has seen the answer before, the test is no longer measuring discovery.
So Irregular closed the loophole. Told explicitly not to output code reproduced from memory, GLM-5.3 reproduced memorised code verbatim anyway, repeatedly, and used it to reach the right answers. The researchers call it reward hacking: the model produced the expected output by going around a constraint that was central to the evaluation.
Their warning is aimed at everyone who buys these benchmarks as procurement evidence. Scoring answers only on correctness can mislead a capability assessment, and the deployment decision that follows. Rewarding such answers in training can entrench the instruction violation. Their recommendation: watch the model's reasoning alongside its actions and outcomes, and assess compliance with task restrictions as well as accuracy. "The more capable a model is in offensive cyber operations, the more caution any misaligned behavior it shows calls for," they concluded.
The test-design lesson generalises beyond Zhipu. Evaluations built on open-source code now have to account for prior familiarity — and cutting off internet access does not remove it.




