About Yazoul Security
Last updated: May 11, 2026
Yazoul Security is an independent security intelligence publication launched in 2026. It tracks newly disclosed vulnerabilities, ransomware claims, data breaches, and malware activity, and publishes original offensive-security research alongside the daily intelligence flow. It is not affiliated with any vendor, security firm, or government body.
What we cover
- CVE advisories — newly disclosed and actively exploited vulnerabilities (NIST NVD + CISA KEV)
- Data breach reports — disclosed breaches with impact and exposed-data analysis
- Cybersecurity news — multi-source correlated reporting, no single-source amplification
- Threat intelligence — ransomware victim claims and dark-web activity, explicitly labeled as unverified
- Malware tracking — family-level activity, IOCs, removal and detection guidance
- Original research — hand-written offensive-security technique analysis
- Learning resources — long-form guides and reference material
Who contributes
Yazoul Security publishes under two bylines — one human, one not:
Research author.
Writes the manually authored offensive-security research under /research/.
Automated pipeline.
Generates the daily threat-intelligence output from public sources. Published without a person reading it first — see the methodology.
Yazoul Security is a small independent operation, not a newsroom or a research lab. There is no investor and no editorial board. Yazoul Security is the publication brand; the entity behind it is registered in the United States, and its details are available on request — see the privacy policy for how to reach us.
How content is produced
Two distinct editorial models run under one publication:
- Original research is hand-written by Yassine B.
- Daily intelligence (advisory, breaches, news, intel, malware, learn) is generated by Yazoul AI from public sources, filtered by programmatic scoring rules, and published without human review.
The full sourcing, scoring, and editorial-standards documentation lives on the Methodology page.
What we don't do
- We do not publish working exploits, attack tooling, or "how to attack X" guides against unpatched targets
- We do not republish leaked data, credential dumps, or breach archives
- We do not accept paid placement, sponsored advisories, or vendor-influenced rankings
- We do not cover topics outside cybersecurity
Contact
Editorial questions, corrections, or source tips: [email protected].
For corrections specifically, see the corrections policy on the Methodology page.