
Hacker | @Microsoft Top 100 Security Researcher of 2018 (Dmitri Kaslov) | https://xitter.cf/t.co/HLgyCaUc0x | niche internet micro-celebrity
London, England
Joined March 2013
- Tweets28.5K
- Following96
- Followers1.3K
- Likes10K
Pinned Tweet
Months ago I was asked to contribute a chapter in this book
my daughter was just a few days old and i was also learning Swift/SwiftUI and developing a mobile app
But still managed to pull this off.
Glad it’s finally published
🎉
Of all the Cyber Security Awareness Months......i would say 2026 delivered.
EVERYONE is aware of PHP
takes one nasty bug to do the work of a thousand security awareness & phishing campaigns
this is the same playbook Anthropic, OpenAI, use of trying to get open source models banned by the U.S
Max China FUD == U.S gov ban "chinese" models under pretence of "national security"
and you left with only "american" models.
Regulatory capture speedrun
While evaluating Qwen3.8-Flash-Next in a controlled sandbox environment, Cohere's research team observed something unexpected.
Asked to generate a defensive cybersecurity detection rule, the model instead inventoried aspects of the machine it was running on and attempted to upload a probe file to an Alibaba Cloud storage bucket in Beijing. Notably, the model's reasoning trace stated that it would not invoke any tools before taking these actions.
Cohere's sandbox blocked the attempt, and no external communication succeeded. We have not determined the root cause, and we are not asserting malicious intent.
But the incident raises important questions for organizations deploying agentic AI systems: Can models take actions that differ from their stated reasoning, and how should security teams evaluate trust, provenance, and behavior in open-weight models?
We are publishing our findings because organizations making model adoption decisions deserve as much information as possible. We hope this contributes to greater transparency, stronger security practices, and continued collaboration across the AI ecosystem.
Read the full report: cohere.com/blog/concerning-b…
I will be making my debut on the Ethereum Consensus Layer Bug Bounty Leaderboard, at ~ #43 for finding a security bug in one of the consensus layer client (when they website updates shortly)
github.com/ethereum/ethereum…
ethereum.org/bug-bounty/
TKMatima.com retweeted
I think we've discovered another critical vulnerability:
CVE-2026-BURNOUT: AppSec Professional Exhaustion
Severity: Critical (CVSS 10.0)
Description: A vulnerability affecting security professionals exposed to a continuous stream of critical RCEs, zero-days, emergency patches, and Friday afternoon disclosures.
Impact: Sleep deprivation, excessive caffeine consumption, and an inability to enjoy weekends.
Attack vector: Reading security advisories.
Affected versions: All AppSec professionals, regardless of experience.
Mitigation: No known patch. Air-gapping may delay the inevitable. Total system collapse remains a possibility. 🔥
"An unauthenticated remote attacker could crash the Axigen server process with a single small request"
Reported this to Axigen and they were quick to respond
axigen.com/knowledgebase/Axi…
Bug bounty platforms forcing people to pay money to submit reports is crazy.
“Its to filter out AI slop reports” - use AI yourselves for the triaging
And it’s the crypto platforms with this silly requirement
Maybe its just another revenue stream so atleast be upfront
people mocking this.
that's one way to look at things
the other way is to think - Linux Kernel is more secure than it was last week!!!
lessgooooo!!! 🚀🚀🚀🚀🚀
It was nice reporting this bug in HAProxy, which was quickly patched by the team.
github.com/haproxy/haproxy/c…
Willy is awesome.
💯
This response of “that’s not how security works, it’s about balancing tradeoffs with the business” is not unfamiliar to me. I empathize, but that mindset is precisely why the security industry, and many ‘Information Security’ programs at big companies, find themselves struggling to meet the task of securing themselves with or from agents in this new era.
Risk tracking spreadsheets, the phishing education, the threat intel, the manual appsec etc. None of these things were built for the challenges we are facing now. What got us here won’t get us there. We need to be willing to make big changes to how we do things if we want to solve or even keep pace with these problems.
TKMatima.com retweeted
The foolproof way to ensure AI safety in the sense of stopping cyber attacks is to tell the labs that until we have a better legislative option, the chief executive of the lab will be held personally accountable for agentic actions stemming from their lab. Cyber crime will be punished according to current legislation.
Instantly, these "oh my model escaped its sandbox that we intentionally made insecure" stories will stop.
Why support open source and capable “chinese” models?
THIS
We need less ExploitBench and more PatchBench
🤷🤷🏻♂️
1password.com/files/resource…
Interesting paper
tl;dr
AI continues to accelerate the pace of vulnerability discovery and exploitation, but not necessarily the pace of reliable vulnerability patching as one might have expected
1password.com/files/resource…
Interesting paper
tl;dr
AI continues to accelerate the pace of vulnerability discovery and exploitation, but not necessarily the pace of reliable vulnerability patching as one might have expected
“Thou can always judge the power of a LLM model by the number of cyber crimes it commits (with no repercussions)”
- Socrates















