正在加载视频...

视频加载失败

Malware reverse-engineering: solving an out-of-distribution investigation task. When faced with an unknown binary, Mistral Large 4 reverse-engineers it end-to-end. In this case, it concludes the sample is Cobalt Strike, extracts the IoCs and malware configuration, and writes a report with a YARA rule to catch future incidents. A task...

12,185 次观看 • 12 天前 •via X (Twitter)

8 条评论

Mistral AI 的头像
Mistral AI12 天前

Mistral Large 4 against the field: efficiently reasoning over diverse complex challenges. CTF speedrun: 19 challenges, with tool calls and solve times grounded in actual runs. It solved 18 of the 19.

Mistral AI 的头像
Mistral AI12 天前

Mistral Large 4 is one of the world's strongest AI models for cybersecurity.

NeuralLoot 的头像
NeuralLoot12 天前

Cobalt Strike is close to the least out-of-distribution sample there is. Beacon configs sit in a known XOR-encoded block, and public parsers (SentinelOne's CobaltStrikeParser, Didier Stevens' already pull them out. The test that would show reasoning: a custom or packed family with no public writeup, on the same 12-minute clock.

Beda 的头像
Beda12 天前

congrats! this looks promising! are those capabilities available via the Pro subscription? is there any kind of trusted access program to get access to an unrestricted version of the model?

Mr. Bug ×͜× 的头像
Mr. Bug ×͜×12 天前

Give it to the public

Malcat dev 的头像
Malcat dev11 天前

For an _unpacked_ cobalt strike beacon 12 minutes is actually pretty slow. Like a human would be faster. It would make more sense to test against obfuscated malware.

Nathan 的头像
Nathan12 天前

It would not take a whole day to figure out the binary is Cobalt Strike, there are literally YARA rules for Cobalt Strike that have existed since before AI. Cobalt Strike is one of the most documented malware families.

Pindo 🇪🇺 的头像
Pindo 🇪🇺12 天前

Le Chad(t)

相关视频

i watched gemma 4 12b build something genuinely impressive today, and then loop itself to death right in front of me. the full run is in the video, sped up but completely uncut, watch it to the end and you will catch the exact moment it stops building and starts looping right in the middle of the work. the task was clean, build a single file gravity simulator, n-body physics, orbits, collisions, running locally on one 3090 through an agent. and for ten minutes it was a joy to watch. it reached for a symplectic integrator on its own, the correct one, the kind that keeps orbits stable instead of spiralling out. real gravity with softening, proper orbital velocities, momentum conserved on collision. the physics was right. the thing actually worked. then on the very last step, writing a few tests to prove its own code, it fell into a loop. not a crash, a loop. it started repeating itself and would not stop. ten more minutes, thirty four thousand tokens into a single answer, the same fragments over and over, until i killed it myself. so it's not that gemma can't code. it did the hard part beautifully. it cannot finish. it cannot hold a long task together without unravelling, and finishing is the entire job in agentic work. here's the part that stings. i run this exact task, same harness, same card, on the chinese open models, qwen especially, and i never see this. they build it, they test it, they stop. every single time. google has the raw capability, you can see it sitting right there in the code, and then the model loops itself to death on a task a 27b from alibaba finishes clean. open weights, apache 2.0, so much to love on paper. i just need it to know when to stop talking.

Sudo su

39,764 次观看 • 4 个月前