Skip to content
nulltapE-reader edition

← All e-reader articles

3 min read

StepSecurity Scans GitHub History and Developer Machines for Planted Files

A new beta matches campaign files across repository refs; enrolled developer devices get a matching view and rule controls. Trace the same finding through both.

Read on the standard site

A suspicious file stands out in a repository tree on a developer laptop.

StepSecurity launched Malicious Files for GitHub in beta on November 3. Its stated job is to find campaign-planted files across an organization’s repository history, including branches, pull requests and tags. The same launch renamed Dev Machine Guard’s Suspicious Files view to Malicious Files and added controls for its detection rules. Teams with GitHub repositories and enrolled developer machines can now follow a suspect file from a commit to a laptop.

The problem starts before a dependency scanner gets a vote. A stolen developer account can push an editor setting or workflow that runs when someone opens a project or triggers a pipeline. StepSecurity cites the Miasma campaign’s planted IDE configuration and the ForceMemo campaign’s force-pushed Python files as examples. The company is describing and evaluating its own product; check Scan Status for your organization’s actual commit and file-version coverage.

A rule follows the planted file

StepSecurity says a repository rule checks file paths and contents together. Its published Miasma example, miasma-ide-autorun-github-setup-js, requires an IDE configuration file, a reference to the loader and an automatic-run condition; two further checks are optional. The named configuration paths include .claude/settings.json and .vscode/tasks.json. The loader file is .github/setup.js, run by Node.js in the attack described by StepSecurity. Use those paths as search pivots and inspect the rule’s required content checks before treating an editor configuration as a detection.

StepSecurity defines a finding as “one file path matched by one rule, across every version of that file.” StepSecurity says its GitHub Findings view lists the branches, pull requests and tags containing the file, the introducing commit and author, matched checks, rule revision and matching blob hashes. Scan Status records commits and file versions scanned, findings, and last and next scan times. Those are the records to preserve before cleanup, particularly if a planted file is buried on a stale ref rather than the default branch.

The StepSecurity documentation hub places Malicious Files under both GitHub and Developer Machines. In Dev Machine Guard, the launch says each file finding has a device, user, OS, file path, SHA-256 hash, rule and first and last seen times. Match the campaign across both views; a repository match names where to remove a file, while a device match points to a machine where it landed. A matching file alone calls for investigating process and credential activity before assigning execution or theft.

Remove every live copy

Filter GitHub Findings by campaign, inspect Found in for each branch, pull request and tag, then inspect Occurrences to identify the pushing account and commit. Preserve the matched path, blob hashes, rule revision and commit history. Search the endpoint Findings view for the same campaign, including devices whose users cloned the affected repository. Review available IDE and process telemetry for execution and account activity for unexpected pushes. StepSecurity’s device Rules page permits organization-wide deactivation; that moves findings to Suppressed and stops the rule scanning, so keep the relevant rule active while checking cleanup.

Remove planted files from the affected refs and devices, then revoke and rotate the pushing account’s credentials and credentials reachable from affected machines from a clean workstation. Protect the branches that matter against renewed force pushes: GitHub says branch protection rules disable force pushes by default, and administrators or bypass roles can be included in restrictions. Apply protection to the actual branch patterns in use and review permitted exceptions; branch protection works on matching branches, while the file investigation still spans pull requests and tags.

Confirm refs and devices cleared

Run a fresh repository scan after removing the file. Check Scan Status for a completed post-cleanup scan and inspect the finding’s Found in list: StepSecurity says a repository finding becomes Vanished once no branch, pull request or tag contains the file, with the record retained for 180 days. Check that affected device findings move to Resolved, rather than Suppressed, with the rule active. Keep the commit and device records with the credential-revocation record. That gives the next responder a starting point if a file or an unauthorized push reappears.

Primary sources