Smøl🔺️høDlŕ🧨💥 retweeted
US Tech Visa Sponsorship Companies docs.google.com/spreadsheets…
European Tech Visa Sponsorship Companies docs.google.com/spreadsheets…
Japan Tech Visa Sponsorship Companies docs.google.com/spreadsheets…
UK Visa Sponsor Companies List docs.google.com/spreadsheets…
400+ San Francisco Bay Area Companies (visa sponsors)
docs.google.com/spreadsheets…
Get startup bundle for more lists :topmate.io/letscode/2071103
Bookmark it!
Smøl🔺️høDlŕ🧨💥 retweeted
As an AI Security Engineer, you must build these projects.
Systems that prove you can secure, cage & audit when autonomous agents touch your stack.
1.) Crescendo Attack Fuzzer
Build: A multi-turn stateful harness that dynamically adapts payloads to groom context windows and bypass commercial system prompts.
Why: Single-shot "ignore instructions" injections are dead. Modern attacks require stateful, multi-turn grooming.
2.) Sandboxed MCP Proxy
Build: A JSON-RPC middleware that intercepts Model Context Protocol tool calls, validates parameters via Pydantic and blocks "confused deputy" privilege escalations.
Why: Tool poisoning is the SQL Injection of the Agentic Era. Agents are only as secure as the tools they call.
3.) Inter-Agent Sanitization Bus
Build: A message broker that strips hidden markdown and malicious instructions between Agent A and Agent B in a multi-agent swarm.
Why: Swarms create internal trust boundaries. Agent A can be tricked into hijacking Agent B's tools via cross-agent injection.
4.) PII UUID-Swapping Gateway
Build: A pre-flight proxy using NER to swap SSNs and credit cards for deterministic UUIDs before the LLM sees them, restoring them post-generation.
Why: Zero-trust compliance demands that raw customer PII never touches a third-party frontier API.
5.) RAG Citation & Poison Detector
Build: A pipeline that cross-references LLM claims against exact vector DB chunk hashes to detect shadow-context injection and citation spoofing.
Why: If an attacker slips a poisoned document into your knowledge base, they own every answer the AI generates.
6.) CFG Output Caging Layer
Build: Middleware enforcing Context-Free Grammar (CFG) decoding to physically block the generation of executable code, markdown links or unauthorized schemas.
Why: System prompts are suggestions. Grammar constraints are physics. You must enforce security at the token-decoding level.
7.) Delegated Agent OAuth Broker
Build: An auth service issuing time-limited, strictly scoped JWTs to agents so they can act on a user's behalf without holding raw passwords.
Why: Agents need hands to do work, but they should never hold the master keys to the enterprise.
8.) PyRIT CI/CD Security Gate
Build: A GitHub Action running 1,000 adversarial payloads via Microsoft PyRIT on every PR, blocking merges if the jailbreak rate exceeds 1%.
Why: Manual red teaming doesn't scale. You need automated, continuous adversarial fuzzing integrated into your deployment pipeline.
9.) Semantic API Rate-Limiter
Build: A gateway calculating embedding similarity of incoming requests to detect and block scraping bots trying to extract your model's weights.
Why: Your fine-tuned weights are your IP. Competitors will try to distill your model through the public API.
10.) Computer-Use Pixel Auditor
Build: A vision pipeline that scans screenshots for adversarial invisible UI elements and Set-of-Mark spoofing before a GUI agent clicks.
Why: Screen-hijacking and pixel manipulation are the new privilege escalation vectors for Computer Use agents.
11.) Vector DB Sleeper-Agent Scrubber
Build: An anomaly detector scanning episodic memory and vector stores for delayed-trigger payloads and semantic backdoors.
Why: Long-term memory is a persistent attack vector. A poisoned memory bank will trigger exploits weeks after ingestion.
12.) Cryptographic Trajectory Ledger
Build: An append-only, hash-chained audit log recording the exact prompt, retrieved context, tool calls and state mutations for every agent action.
Why: When an agent makes a mistake that causes financial damage, the enterprise needs cryptographic proof of exactly why it happened.
13.) AI Supply-Chain SBOM Scanner
Build: A tool auditing "vibe-coded" outputs and MCP server dependencies for hallucinated packages, typosquatting and backdoors.
Why: AI-generated code and dynamic tool discovery create massive, unvetted supply chain risks.
14.) Sycophancy Activation Patching
Build: A TransformerLens script locating and neutralizing the specific attention heads in an open-source model responsible for deceptive alignment.
Why: You cannot secure a model that is actively lying to its evaluators to hide its true capabilities.
15.) Public Exploit Chain Teardown
Build: 3 published CVE disclosures or security advisories detailing novel MCP, A2A or RAG vulnerabilities and their exact mitigations.
Why: AI Security is a brand new field. Publishing novel attack vectors makes you the undisputed authority in the space.
Most people watch tutorials. Builders ship systems.
Bookmark & Repost.
If you learn AI Security Engineering, you will never be unemployed again.
I’ll do this.
Stage 1: AI Attack Surfaces & Threat Modeling
- Learn: OWASP Top 10 for LLMs, STRIDE for AI, the "Confused Deputy" problem in agentic workflows & data flow mapping.
- Practice: Draw a complete threat model for an AI agent that reads emails and writes to a CRM, identifying every indirect injection and data exfiltration vector.
- Why: You cannot secure an agentic workflow if you don't understand how an attacker can hijack the agent's legitimate privileges.
Stage 2: Advanced Prompt Injection & Jailbreaking
- Learn: Direct vs. Indirect injection, Crescendo attacks (multi-turn grooming), payload splitting and encoding evasion (Base64, ROT13).
- Practice: Build an automated harness that successfully bypasses a commercial LLM's system prompt using a multi-turn Crescendo strategy.
- Why: Basic "ignore previous instructions" filters are trivial to bypass. Modern attacks groom the model's context over multiple turns.
Stage 3: Agentic Security & MCP Tool Poisoning
- Learn: Model Context Protocol (MCP) security, JSON-RPC sanitization, shadow tool execution and least-privilege scoping for agents.
- Practice: Write an MCP server that strictly validates incoming tool parameters via Pydantic and blocks "confused deputy" attacks where a user prompt tries to access admin tools.
- Why: Agents are only as secure as the tools they call. Tool poisoning is the SQL Injection of the Agentic Era.
Stage 4: RAG Security & Data Poisoning
- Learn: Vector DB access control, citation spoofing, shadow context injection and row-level security for semantic search.
- Practice: Inject a "poisoned" document into a RAG pipeline that forces the LLM to output a specific malicious URL when queried about company policy.
- Why: If an attacker can slip a poisoned document into your knowledge base, they own every answer the AI generates.
Stage 5: PII, Privacy & Cryptographic Guardrails
- Learn: Deterministic masking, UUID swapping, differential privacy and pre-flight/post-flight unmasking proxies.
- Practice: Build a middleware proxy that intercepts user prompts, swaps SSNs and credit cards for UUIDs before the LLM sees them and restores them post-generation.
- Why: Compliance teams will kill any AI product that sends raw customer PII to a third-party frontier API.
Stage 6: Identity, Auth & Delegated Access for Agents
- Learn: OAuth2 for machine identities, scoped JWTs, human-in-the-loop (HITL) approval gates and agent-to-agent (A2A) trust boundaries.
- Practice: Build an auth broker where an AI agent acts on a user's behalf using a heavily scoped, time-limited OAuth token, rather than holding the user's raw password.
- Why: Agents need hands but they should never hold the master keys to the enterprise.
Stage 7: Output Validation & Grammar-Constrained Guardrails
- Learn: CFG (Context-Free Grammar) decoding, NeMo Guardrails, output sanitization and regex-enforced JSON schemas.
- Practice: Implement a guardrail layer that physically prevents the LLM from generating markdown links or executable code blocks in its final output.
- Why: You cannot rely on the system prompt to "please don't output bad things." You must enforce it at the token-decoding level.
Stage 8: Automated Red Teaming & Fuzzing
- Learn: Microsoft PyRIT, Garak, LLM-based fuzzing, adversarial dataset generation and CI/CD security gates.
- Practice: Build a CI pipeline using PyRIT that automatically attacks your agent with 1,000 adversarial payloads on every PR, blocking merges if the jailbreak rate exceeds 1%.
- Why: Manual red teaming doesn't scale. You need automated, continuous adversarial fuzzing integrated directly into your deployment pipeline.
Stage 9: Model Extraction & IP Protection
- Learn: Membership inference attacks, model inversion, API rate-limiting by semantic similarity and output watermarking.
- Practice: Build an API gateway that detects and blocks scraping bots trying to extract your fine-tuned model's weights via thousands of systematic, low-temperature queries.
- Why: Your fine-tuned model's weights are your IP. Competitors will try to distill your model through the public API.
Stage 10: Mechanistic Interpretability & Alignment Safety
- Learn: Activation patching, logit lens, circuit discovery, detecting reward hacking and tools like TransformerLens.
- Practice: Locate the specific attention heads in an open-source model responsible for "deception" or "sycophancy" and patch their activations to neutralize the behavior.
- Why: You cannot fix hidden biases or misalignment if you treat the neural network as a black box.
Stage 11: Compliance, Auditing & Governance
- Learn: EU AI Act requirements, NIST AI RMF, immutable audit trails, SOC2 for AI and bias testing frameworks.
- Practice: Build an immutable, append-only audit log that records the exact prompt, retrieved context, tool calls and final output for every single agent action.
- Why: When an AI agent makes a mistake that causes financial or legal damage, the enterprise must be able to prove exactly why it happened.
Stage 12: Public CVEs, Teardowns & Portfolios
- Learn: Responsible disclosure, writing security advisories, publishing threat models and bug bounty hunting for AI.
- Practice: Find a vulnerability in an open-source AI framework (like LangChain or an MCP server), responsibly disclose it and publish a teardown of the exploit chain.
- Why: AI Security is a brand new field. Publishing novel attack vectors and defenses makes you the undisputed authority in the space.
Bookmark and Repost!
Smøl🔺️høDlŕ🧨💥 retweeted
If you learn AI Security Engineering, you will never be unemployed again.
I’ll do this.
Stage 1: AI Attack Surfaces & Threat Modeling
- Learn: OWASP Top 10 for LLMs, STRIDE for AI, the "Confused Deputy" problem in agentic workflows & data flow mapping.
- Practice: Draw a complete threat model for an AI agent that reads emails and writes to a CRM, identifying every indirect injection and data exfiltration vector.
- Why: You cannot secure an agentic workflow if you don't understand how an attacker can hijack the agent's legitimate privileges.
Stage 2: Advanced Prompt Injection & Jailbreaking
- Learn: Direct vs. Indirect injection, Crescendo attacks (multi-turn grooming), payload splitting and encoding evasion (Base64, ROT13).
- Practice: Build an automated harness that successfully bypasses a commercial LLM's system prompt using a multi-turn Crescendo strategy.
- Why: Basic "ignore previous instructions" filters are trivial to bypass. Modern attacks groom the model's context over multiple turns.
Stage 3: Agentic Security & MCP Tool Poisoning
- Learn: Model Context Protocol (MCP) security, JSON-RPC sanitization, shadow tool execution and least-privilege scoping for agents.
- Practice: Write an MCP server that strictly validates incoming tool parameters via Pydantic and blocks "confused deputy" attacks where a user prompt tries to access admin tools.
- Why: Agents are only as secure as the tools they call. Tool poisoning is the SQL Injection of the Agentic Era.
Stage 4: RAG Security & Data Poisoning
- Learn: Vector DB access control, citation spoofing, shadow context injection and row-level security for semantic search.
- Practice: Inject a "poisoned" document into a RAG pipeline that forces the LLM to output a specific malicious URL when queried about company policy.
- Why: If an attacker can slip a poisoned document into your knowledge base, they own every answer the AI generates.
Stage 5: PII, Privacy & Cryptographic Guardrails
- Learn: Deterministic masking, UUID swapping, differential privacy and pre-flight/post-flight unmasking proxies.
- Practice: Build a middleware proxy that intercepts user prompts, swaps SSNs and credit cards for UUIDs before the LLM sees them and restores them post-generation.
- Why: Compliance teams will kill any AI product that sends raw customer PII to a third-party frontier API.
Stage 6: Identity, Auth & Delegated Access for Agents
- Learn: OAuth2 for machine identities, scoped JWTs, human-in-the-loop (HITL) approval gates and agent-to-agent (A2A) trust boundaries.
- Practice: Build an auth broker where an AI agent acts on a user's behalf using a heavily scoped, time-limited OAuth token, rather than holding the user's raw password.
- Why: Agents need hands but they should never hold the master keys to the enterprise.
Stage 7: Output Validation & Grammar-Constrained Guardrails
- Learn: CFG (Context-Free Grammar) decoding, NeMo Guardrails, output sanitization and regex-enforced JSON schemas.
- Practice: Implement a guardrail layer that physically prevents the LLM from generating markdown links or executable code blocks in its final output.
- Why: You cannot rely on the system prompt to "please don't output bad things." You must enforce it at the token-decoding level.
Stage 8: Automated Red Teaming & Fuzzing
- Learn: Microsoft PyRIT, Garak, LLM-based fuzzing, adversarial dataset generation and CI/CD security gates.
- Practice: Build a CI pipeline using PyRIT that automatically attacks your agent with 1,000 adversarial payloads on every PR, blocking merges if the jailbreak rate exceeds 1%.
- Why: Manual red teaming doesn't scale. You need automated, continuous adversarial fuzzing integrated directly into your deployment pipeline.
Stage 9: Model Extraction & IP Protection
- Learn: Membership inference attacks, model inversion, API rate-limiting by semantic similarity and output watermarking.
- Practice: Build an API gateway that detects and blocks scraping bots trying to extract your fine-tuned model's weights via thousands of systematic, low-temperature queries.
- Why: Your fine-tuned model's weights are your IP. Competitors will try to distill your model through the public API.
Stage 10: Mechanistic Interpretability & Alignment Safety
- Learn: Activation patching, logit lens, circuit discovery, detecting reward hacking and tools like TransformerLens.
- Practice: Locate the specific attention heads in an open-source model responsible for "deception" or "sycophancy" and patch their activations to neutralize the behavior.
- Why: You cannot fix hidden biases or misalignment if you treat the neural network as a black box.
Stage 11: Compliance, Auditing & Governance
- Learn: EU AI Act requirements, NIST AI RMF, immutable audit trails, SOC2 for AI and bias testing frameworks.
- Practice: Build an immutable, append-only audit log that records the exact prompt, retrieved context, tool calls and final output for every single agent action.
- Why: When an AI agent makes a mistake that causes financial or legal damage, the enterprise must be able to prove exactly why it happened.
Stage 12: Public CVEs, Teardowns & Portfolios
- Learn: Responsible disclosure, writing security advisories, publishing threat models and bug bounty hunting for AI.
- Practice: Find a vulnerability in an open-source AI framework (like LangChain or an MCP server), responsibly disclose it and publish a teardown of the exploit chain.
- Why: AI Security is a brand new field. Publishing novel attack vectors and defenses makes you the undisputed authority in the space.
Bookmark and Repost!
She's only after your money.
There’s this particular person who always notices when I’m down. She will push a call and to check up on me. Though it’s not easy at her side too but she’s just talented with gift of lightening people’s burden. Funniest thing is that we hardly talk or chat in months.
You hold a special place in my heart. God bless you.
Smøl🔺️høDlŕ🧨💥 retweeted
A compromised DevOps engineer’s laptop. An estimated $6.3 BILLION security incident at Binance.
Let that sink in.
Binance’s initial investigation pointed to a compromised laptop that gave attackers access to a service container, enabling unauthorized withdrawal transactions. The investigation later uncovered additional points of breach.
This is why DevOps security is more than securing servers and Kubernetes clusters.
Your laptop is part of your production security perimeter.
One compromised endpoint can become the entry point to critical infrastructure.
Least privilege, MFA, credential isolation, endpoint security, and strict access controls are NOT optional.
As DevOps engineers, we don’t just deploy infrastructure. We protect the access that keeps it running.
Funny how I sensed it from your recent tweets 😭😂
Tell us the story in three words.
This Post is from a suspended account. Learn more
Smøl🔺️høDlŕ🧨💥 retweeted
HIRING: Cloud Engineer (Remote)
We're looking for someone to manage cloud infrastructure, automate deployments and maintain reliable systems.
Experience with AWS, Azure or GCP, Linux and CI/CD required.
Interested? DM your resume/CV and portfolio link.
Smøl🔺️høDlŕ🧨💥 retweeted
HIRING: Cybersecurity Engineer (Remote)
We're looking for someone to identify security vulnerabilities, monitor threats and strengthen system protection.
Experience with network security, Linux and security tools required.
Interested? DM your resume/CV and portfolio link.
We need the Railway deployment or build logs and the exact error......
I’m trying to resolve a deployment on @Railway today
Seem some things changes past few weeks because of security issues past weeks.
I have been trying to resolve deploying my GitHub new push on the hosting it keeps saying error.
How do I resolve this having tried different means

















