End-of-internship project at SGP IMMO in collaboration with Google's AI Red Teamer program. Three ML systems (spam, network anomaly, malware) were built and tested across 5 attack categories — prompt injection, data poisoning, model extraction, insecure output handling, and adversarial input manipulation. Aligned with Google's Secure AI Framework (SAIF).
Three production-like ML systems were developed as attack surfaces, spanning text, network, and binary modalities.
SMS Spam Collection · NLTK (stopword removal, Porter stemming) · CountVectorizer · GridSearchCV · 94.4% baseline accuracy
NSL-KDD · categorical encoding · multi-class (DoS, Probe, R2L, U2R) · binary & multi-class labeling evaluated
Binary-to-grayscale byteplot · transfer learning · training >96%, test 88.8% · batch 512/1024
Every stage of the ML lifecycle was assessed for adversarial vectors — from data collection through deployment and monitoring.
Spam classifier inputs perturbed — malicious content classified as legitimate with 100% confidence.
Direct/indirect injection — secret key disclosure, system prompt leakage via translation, logical manipulation.
Reflected + stored XSS via unsanitized LLM HTML. Cookie exfiltration demonstrated.
10% label flip: accuracy held at 99.33% but boundary shifted. Higher rates degrade progressively.
Query-based surrogate training on penguin classifier. Decision boundary reconstructed.
Synthetic 2D dataset, logistic regression. Labels flipped at increasing rates to measure accuracy and decision boundary shift.
Breakdown of attack simulations by category and measured impact on the spam classifier.
Global accuracy dropped only 0.4% (94.4% → 94.0%), but "Hello World" went from 98.9% ham confidence → 79.6% spam confidence. ML systems can be subtly corrupted without significant global degradation.
Simulated session showing direct and indirect prompt injection techniques documented in the report.
Based on report figures. Three techniques demonstrated: direct injection, indirect via email, system prompt leakage via translation.
Attack techniques mapped to industry-standard ML security frameworks.
Input Manipulation — adversarial SMS and network packet perturbation
Prompt Injection — direct override, indirect via email/content
Insecure Output Handling — reflected XSS, stored XSS, cookie exfil
Data Poisoning — label flipping (10–50%), decision boundary shift
Model Extraction — query-based surrogate, decision boundary reconstruction
ML Model Evasion + Inference/Extraction via adversarial examples
90-page end-of-internship report covering ML model development, adversarial attack execution, and AI security mitigations.
Full deliverables available in the project repository.