# Semgrep: Scan failures with exit code 7 due to invalid rule

- Impact (vendor’s label): major
- Status: resolved
- Started: 2026-06-25 21:32 UTC · Resolved: 2026-06-25 22:27 UTC · Duration: 56 min
- Updates: 3 · Affected components: Scans and CI/CD, semgrep.dev - Scans and CI/CD, Managed Scans, semgrep.dev - Managed Scans
- [Vendor status page: https://stspg.io/vkkncvyrv3l8](https://stspg.io/vkkncvyrv3l8)
- [Company: Semgrep](https://rewindex.com/company/semgrep.md)

## Summary

Semgrep reported a major incident causing widespread exit code 7 scan failures in Managed Scans and Scans and CI/CD from 2026-06-25 21:32 UTC to 2026-06-25 22:27 UTC (55 min). A bad AI skills rules release caused the failures; Semgrep removed "skills.behavioral.skill-destructive-commands.skill-destructive-commands" and confirmed scans were running normally. _(machine-written, sol)_
## Timeline of updates

- **identified** 2026-06-25 21:32 UTC: We have observed widespread scan failures relating to a bad release of AI skills rules. We are working to fix the issue.  To prevent the issue in the meantime, you can disable the "skills.behavioral.skill-destructive-commands.skill-destructive-commands" rule in your Semgrep policies.
- **monitoring** 2026-06-25 22:14 UTC: We have removed the problem rule ("skills.behavioral.skill-destructive-commands.skill-destructive-commands") and we are seeing scan behavior recover. We are continuing to monitor for full recovery.
- **resolved** 2026-06-25 22:27 UTC: This issue has been resolved. Scans are now running normally.

## Rewindex changes for this incident

- 2026-06-25 21:32 UTC: [Major incident: Scan failures with exit code 7 due to invalid rule](https://rewindex.com/change/i2f8b9a4919a0ab.md)


---
Canonical: https://rewindex.com/company/semgrep/incidents/p8222qljjxf1 · Markdown: https://rewindex.com/company/semgrep/incidents/p8222qljjxf1.md · JSON: https://rewindex.com/api/v1/companies/semgrep/incidents/p8222qljjxf1 · Generated 2026-10-18T09:43:34.677Z