π¨ Attackers break out in just 29 minutes. Can your team keep up? Join our FREE Live Breach webinar to explore incident response, common mistakes, and realistic simulations.
π Tuesday, 10 Nov | 3 PM GMT
π Save your seat: https://t.co/SGe02BxC4h
π¨ New threat just dropped! Drupal Commerce CVE-2026-118539 is yours to exploit. π
Break in, trace the attack, and verify the fix.
π Now live on TryHackMe MAX: https://t.co/Jj2zCRGZQb
Pentesting vs Red Teaming. βοΈ Same target, different missions.But whatβs the actual difference? π
We've broken it down for you. π π₯ Time to put your offensive skills to the test. Start hacking: https://t.co/Fw89JP0uiH
π§΅ Hereβs what youβll practise in Detecting Persistent Account Manipulation:
π Detect account manipulation used for persistence
π€ Identify suspicious local and domain account changes
π Use Windows Event Logs and DFIR artefacts to investigate account-based persistence
π The quietest persistence isnβt malware. Itβs a new account, a reset password, or one extra group membership. Learn to spot account manipulation before the attacker comes back π
π§΅ The hardest persistence to catch doesnβt look like an attack. It looks like IT. A new user. A re-enabled account. One extra group membership. No malware to flag, just a legitimate mechanism used by someone who shouldnβt have it.
Check who has access, not just what is running. π
Almost 50% of AI-generated code is vulnerable... yup you read that right...
It means most companies are introducing MORE vulnerabilities than EVER, at a time when itβs never been easier for threat actors to pentest at scale. Especially scary given theyβre shipping more than ever, and few actually read what AI is generating.
To explain the attached image: the line graph on the right shows that from 2023 to 2026, syntax errors (grey line) improved a lot, while secure code generation only marginally improved (red line). The table on the left shows the security pass rate (higher is better). Veracode, who put the report together, tested code snippets generated by different models to see how much of it was vulnerable.
Some vulnerability categories are far more common than others. e.g. SQLi had a high security pass rate at 83% (bc its easier to identify just by code), but XSS' pass rate was 15%. It means we'll see more of one vulnerability category over time.
In fact, even prompting "make this more secure" or "fix X vulnerability" in many cases found that it made the app less secure.
This means that:
1οΈβ£ More vulns are being shipped than ever
2οΈβ£ AI canβt reliably fix its own security flaws
3οΈβ£ You need to test at both the code and app level
4οΈβ£ And test regularly, triggered by critical actions like deploys.
NoScope does exactly this.
I'll link the research in the comments - including a presentation that goes over this in more depth we gave a few weeks ago.
When I heard almost 50% of AI-generated code was vulnerable, I didnβt believe it. So I read the research and tested it myself..
@tryhackme
π΅οΈ Every attacker leaves footprints. Can YOU find them? π£ We've rounded up 5 beginner-friendly Digital Forensics & Incident Response (DFIR) projects to help you think like an investigator and sharpen your hands-on cyber skills. π»
π Save this for your next lab session and go get hacking: https://t.co/A0cJsIw5Y1