Detecting and removing dangerous secrets on workstations before Shai-Hulud does
The article discusses the importance of detecting and removing dangerous secrets from developer workstations to prevent credential theft. It highlights the use of open-source tools like bagel and Fleet to automate the scanning and compliance checking process. The proposed solution aims to enhance security measures for both technical and non-technical users in organizations.
- ▪Credential theft from developer workstations is a growing concern due to the increasing attack surface.
- ▪Bagel is an open-source tool that scans for secrets in user directories and outputs results in JSON format.
- ▪Fleet is an open-source platform that uses osquery for telemetry and can integrate with other tools for compliance checking.
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Recyclebin.zip |
| Canonical URL | https://recyclebin.zip/posts/2026-05-25-secret-scanning-fleet-bagel/ |
| Publication time | Mon, 25 May 2026 19:16:29 +0000 |
| Retrieval time | 2026-05-25T19:37:40.493Z |
| Last seen | 2026-05-25T19:37:40.493Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | GutpbFCeTPev |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
Detecting and removing dangerous secrets on dev workstations before Shai-Hulud does2026-05-25Guillaume RossCredential theft from developer workstations#Let’s use a combination of open-source tools to detect problematic clear-text secrets on workstations and to ensure they’re not so easy for malware/scripts to steal.PyPI, npm, VS Code Extensions, OpenVSX, brew and other package managers expand the attack surface on workstations. While companies still lie to themselves that “all code changes are reviewed”, millions of developers have code execution access to workstations, and those developers can get compromised by various threat actors.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Recyclebin.zip.
Discussion
0 commentsMore from Recyclebin.zip
