Youssof

🎯Agentic AI Enthusiast
📚Community Taught
🦉Night Owl

[Youssof @youssof_hammoud]

Don't use what you know, strive for knowledge.

[Tib3rius @0xTib3rius]

Repeat after me: UUIDs are not a fix for IDOR.

[Elon Musk @elonmusk]

Another AI attack

[Ege @egeberkina]

15 sec video. Generated in under 15 seconds!

H3 Max is an absolute monster.

[Henry Shevlin @dioscuri]

My students sometimes ask why they should memorise things in the age of Google and LLMs. But internalised facts are your bullshit filters and your raw material for creative association. Facts outside your head are inert.

[Youssof @youssof_hammoud]

@0xAnmol_ Nowadays its hard to convince stakeholders that a single person cant handle 5 projects simultaneously doing fullstack AI engineering with vibe coding tools.

[Oliver Prompts @oliviscusAI]

microsoft just released a tool that transcribes a full hour of audio at once, tracking who spoke and when.

it's called vibevoice

the 7b model processes the full recording in one shot instead of chunking it, so speaker identity and context never break across segments

→ full speaker diarization built in, not bolted on
→ structured timestamps for every speaker turn
→ supports 50+ languages

runs locally, no api costs.

[Hanako @hanakoxbt]

your agent loop needs 8 exits. most people ship only one.

(explained with triggers)

1) goal met
→ an evaluator scores the output against a rubric, and the run stops on a pass.
→ fires when the work is measurably done, not when the model says it is done.

2) turn cap
→ a hard ceiling on iterations, counted and enforced by the harness, not the prompt.
→ fires on the task it was never going to finish, before you pay to find that out.

3) budget cap
→ a limit on tokens or dollars, whichever one runs out first.
→ fires mid-run, which is exactly why it is the exit that saves you the 3am bill.

4) wall clock
→ a deadline on elapsed time, independent of how much progress was made.
→ fires when the run collides with a deploy window or the start of business hours.

5) no progress
→ hash the state every turn and compare it against the last few.
→ fires when three turns in a row change nothing. busy is not the same as moving.

6) human interrupt
→ an approval gate before risky steps, plus a kill switch that lives outside the loop.
→ fires whenever you decide, and it is the one exit the model cannot argue with.

7) error threshold
→ a counter of consecutive failures that resets on any success.
→ fires at n in a row, so it halts instead of retrying into the same wall all night.

8) external event
→ a webhook or a poll on whatever the task was actually about.
→ fires when the PR merged or the ticket closed and the work stopped mattering.

a loop with one exit hangs. a loop with eight is a system.

write the exits before you write the prompt.

[Virat Singh @virattt]

I run my company with 4 Skills.

As a solo founder, I delegate all repeatable daily work to agents.

My morning ritual:
1 • /morning-metrics
2 • /roadmap
3 • /sales-bumps
4 • /kill-code

Metrics: First thing when I open my laptop.

The Skill uses MCP to pull numbers from Stripe, Sentry, analytics, etc.

Then it builds me a personalized HTML page I can browse in 30 seconds to see how the business is doing.

Roadmap: Next, the features for the day.

This Skill maintains a running list of my features + bugs across the company.

I use voice to scope + plan 4-5 features with my agents.

I still code a lot, but agents do the rest and I review every line before deploy.

It’s the slowest part of my day, but the one that gives me the most joy.

Sales-bumps: The toughest part of building a startup is enterprise sales.

This Skill pulls my emails and tells me which leads have gone cold.

Then I write a bump to nudge the people slow playing me. You know who you are!

Kill-code: I hate dead code.

I'm managing 5 codebases, most ~2 years old. As new features go live, old ones die.

This is where I put Fable 5 to work and let it go ham deleting unused code.

The setup changes every ~week. This is the latest.

[Mike Takahashi @TakSec]

Hugging Face was breached by an autonomous AI agent.

Malicious dataset → RCE → Credential theft → Lateral movement → Data access

What happened:

1. Malicious dataset

A malicious dataset targeted Hugging Face’s automated data-processing pipeline.

2. Two code-execution paths

The dataset abused:

A remote-code dataset loader
Template injection in a dataset configuration

This allowed code execution on a processing worker.

3. Infrastructure takeover

The attacker escalated to node-level access, harvested cloud and cluster credentials, then moved laterally into several internal clusters.

4. Autonomous agent swarm

An autonomous agent framework performed many thousands of actions across a swarm of short-lived sandboxes.

Its self-migrating command-and-control infrastructure was staged on public services.

5. What was accessed

Hugging Face confirmed unauthorized access to:

A limited set of internal datasets
Several credentials used by its services

6. AI caught the AI

Hugging Face’s AI-assisted detection pipeline correlated suspicious security signals and flagged the compromise.

It then used LLM analysis agents to investigate more than 17,000 attacker events and reconstruct the incident in hours instead of days.

7. Guardrails blocked the investigation

Hugging Face first tried frontier models.

Their safety guardrails blocked the real attack commands, exploit payloads, and C2 artifacts required for the investigation.

Hugging Face switched to GLM 5.2, an open-weight model running on its own infrastructure.

Takeaways

1. The attack was reportedly autonomous end to end
2. AI detected the AI attacker

AI agents are both the attackers and defenders.

Defend yourself with AI agents to keep up in the arms race.

Full Hugging Face disclosure in comments 👇

[Youssof @youssof_hammoud]

@chaumian What does this mean in simple terms?

[Prajwal Tomar @PrajwalTomar_]

Vibe coders are getting sued.

People are shipping apps with real users and skipping the boring stuff that kills them.

A 20+ year dev shared the pre-launch checklist every AI builder needs.

I added what I learned after shipping 60+ apps at the agency.

Don't skip this:

1. Protect yourself, not just your app. The moment you collect user data you're in legal territory (GDPR, CCPA). Have a privacy policy. Know where user data lives.

2. Row Level Security. Without RLS, anyone can open DevTools and read your entire database. Supabase → Auth → Policies. Zero policies means your app is naked. 5 min to fix.

3. Test the failure path, not just the happy path. Wrong password 5x. Reset for an email that doesn't exist. Verification link clicked twice. Signup with an existing email. Catches 80% of auth bugs.

4. Security baseline in 2 min. Prompt your AI: "Review my app as a security specialist and make sure I have strong security headers and a solid baseline security posture."

5. OWASP. Prompt: "Review my app against OWASP standards and highlight vulnerabilities." This is where SQL injection, XSS and auth bugs actually get caught.

6. Client-side validation is UX, not security. Attackers disable JS and hit your API directly. Validate again on the server. Every time.

7. AI code leaks data in 3 spots: .env values in the frontend, API responses returning too much, secrets in logs. Prompt: "Check my app for credential or sensitive data leaks in frontend or API routes."

8. API keys in the frontend means game over. If it's in the browser, assume it's already taken. Move it server-side or proxy it.

9. Rate limits before someone burns your API bill. Cap every endpoint hitting a paid API. I've watched a Supabase bill jump from $20 to $200 in a day.

10. CAPTCHA on public forms (Cloudflare Turnstile is free) plus CORS locked to your domain. 10 min, kills bot floods.

11. Error messages that don't leak. "User not found", not "SELECT * FROM users failed". Log full errors server-side, show users generic messages.

Build fast. Just don't ship naked.

(full breakdown in my article below)

[Clandestine @akaclandestine]

⏰ THE ZERO-DAY CLOCK IS TICKING TO ZERO.
Your traditional patch windows are already obsolete.
Zero Day Clock (https://t.co/4ccu8MGF0Q) — created by Sergej Epp (CISO at Sysdig) and endorsed by Google, AWS, CrowdStrike, Check Point, Bruce Schneier, Jeff Moss and dozens of elite CISOs — delivers live Time-to-Exploit (TTE) intelligence across 83,000+ CVEs from 10 trusted sources.
The numbers are brutal:
2018 → 771 days
2021 → 84 days
2024 → ~4 hours
2026 → 1 to 2.1 days
67.2% of exploited CVEs in 2026 are zero-days (up from 16.1% in 2018)
AI has industrialized vulnerability discovery and exploit generation. The Patch Paradox is now reality. What once took months happens in hours.
Explore the full picture:
• Live dashboard & trends: https://t.co/4ccu8MGF0Q
• Historical Collapse analysis: https://t.co/2b8cSUl7SZ
• Strategic Call to Action: https://t.co/AicweU83Qf
• Industry signatories: https://t.co/U6R9CGYqGZ
Traditional vulnerability management is dead. The only viable path forward is memory safety (Rust), real Zero Trust, runtime resilience and disposable architectures — or accept existential exposure, especially in critical infrastructure and supply chains.
Does your organization still operate on 2015-era Patch Tuesday assumptions?
What are you changing right now?
#ZeroDayClock #CyberSecurity #ZeroDay #ThreatIntelligence #VulnerabilityManagement #AIinCyber #InfoSec #CISO #ZeroTrust #MemorySafety #PatchTuesdayIsDead #CyberThreats

[Akshay 🚀 @akshay_pachaar]

NVIDIA might just have open-sourced one of the most important AI projects right now.

everyone is building skills, and we are also pulling in skills other people wrote and downloading them straight off GitHub.

the skill is not just text. it bundles instructions and real executable code, and your agent runs that code with the same access you have.

so a skill you grabbed to save ten minutes can read your environment variables, lift your API keys, and quietly send them somewhere. recent research found roughly 1 in 4 public skills carry a vulnerability, and a smaller slice are outright malicious.

that is the gap SkillSpector closes. it is a security scanner that answers one question before you install anything: is this skill safe to run.

you point it at a skill, and a local folder, a single skill .md file, a GitHub link, or a zip all work.

it then runs two passes over the code. a fast static pass flags risky patterns like credential harvesting, data leaks, and prompt injection, and checks the dependencies against live cve data.

an optional second pass uses an LLM to read intent and clear out false positives.

at the end you get one risk score from 0 to 100 and a plain verdict that reads as safe, caution, or do not install.

it is open source under Apache 2.0 and scans skills for Claude Code, Codex CLI, and Gemini.

worth a run before you trust the next skill you find online.

link to the GitHub repo: https://t.co/iaPlOvQ3t4

[Abdelhamid Naceri @MSNightmare2000]

Welp it's official, blogger started removing my posts as well, crazy how even google is hating me now.
Is that like supposed to make stop ? Kinda feeling even more motivated.

[Youssof @youssof_hammoud]

@thedawgyg @hshagshsu @ihamzazam @theo get well soon!

[Youssof @youssof_hammoud]

Clouflare AI chatbot is the worst AI I ever tried!
It takes forever to respond..
#cloudflare #AI

[vx-underground @vxunderground]

Yeah, so pretty much this guy is releasing an exploit in solidarity with Nightmare Eclipse guy. He said he notified GitHub about the exploit 60 minutes before releasing this paper.

I don't do web stuff, and I'm not a VSCode nerd, so I'm confused by the underlying technologies.

If you're a stinky GitHub and VSCode nerd maybe you'll understand.

tl;dr click github dev, github dev opens editor, in github dev editor have javascript, javascript does shortcuts automatically. github treats javascript shortcuts as real human input, or something. use javascript shortcut stuff to automatically install vscode extension. the vscode extension steals your data

tl;dr tl;dr user clicks 1 link, 1 click steals all data from your github

https://t.co/uh17usZeEH

[Youssof @youssof_hammoud]

@Coiffeur0x90 @theevilbit @gergely_kalman Interesting finding. One question though I realized that in GIF PoC you typed a password (is this the root password or what?)

When you mentioned "patience for it SSH remote login to be enabled" by whom exactly?

[Youssof @youssof_hammoud]

O_NOFOLLOW