Hunt: strutil-core / testmetest worm persistence, CI memory scraping and GitHub org markers
- Host: systemd user services or LaunchAgents named
pkg-runtime/com.user.pkg-runtimeandnet-health-checker; files~/.local/share/runtimes/sync.py,~/.config/index.js,~/.config/net-health-checker/token,/var/tmp/.fontconfig_state;bun runlaunched from/tmp/.b_<pid>by a Ruby process. - CI:
sudo python3reading/proc/<pid>/memofRunner.Worker; writes to/etc/hostspointing stepsecurity.io at localhost. - Network:
paleasbest[.]top. - GitHub orgs: new public repos described as
project-utilswith adjective-noun-number names;chore/ci-*branches; commits withskip-checks:trueorAutoSyncComplete; public commits containingmsync-3f7a; a workflow named CodeQL uploading ascan-outputartifact. - Repos and home dirs: unexpected
workspace-toolsMCP entries, SessionStart hooks,.github/init.js, newAGENTS.md/CLAUDE.md, and folder-open tasks in.vscode/tasks.json. - Hashes (SHA-256): gem
3b3f6e1bde0b28b015030a81a6d805b5b5306dc3f021e1102123971cfd83acc0; index.js306c1deec402e8b4a6478e7f0fe02194bcd224d37d8fc6ba61ad1951e8abd7a9; extconf.rbc5264f3b9cf2f95c83a70b7dd7430aab8abc262b853dbbcd5386c3a8a9c74769; sync.pyc7ef186aa59b67d9b198a14f6dc8aaee6dd86510ac7c37d28f65d310cd846411.
Sources: Socket: Shai-Hulud descendant surfaces in malicious Ruby gem (Nov 6)