1-minute read
What a defender needs to know
StepSecurity launched Malicious Files for GitHub in beta, describing a scan of repository history across branches, pull requests and tags. It also renamed Dev Machine Guard’s Suspicious Files view and added rule controls for enrolled developer devices. A planted editor setting can trigger code when a developer opens a repository; a dependency manifest scan would miss that path.
The company’s example Miasma rule requires an IDE configuration path, a loader reference and an automatic-run condition. Search for .claude/settings.json, .vscode/tasks.json and loader file .github/setup.js as separate investigation pivots; a path match by itself is insufficient. In GitHub Findings, use Found in to locate each affected ref and Occurrences for the introducing commit and account. Save the matched blob hashes, rule revision and scan time. Match the campaign in device Findings and review process telemetry and account activity before assigning execution or theft.
Remove the file from affected refs and devices. Revoke and rotate credentials of the pushing account and those reachable from affected machines using a clean workstation. Protect relevant branches from force pushes, including privileged exceptions where needed. Run a fresh repository scan: expect a Vanished finding with an empty Found in list, and Resolved device findings with the rule still active. A Suppressed result follows rule deactivation across devices; use Resolved to track file cleanup.
