حماية مفاتيح API من إضافة VS Code ضارة
GitHub confirmed that attackers stole data from around 3,800 internal code repositories due to a compromised VS Code extension. The breach highlights that developers' devices and tools can be the most vulnerable points, rather than the cloud itself. Developers are advised to implement better security practices to protect API keys and sensitive information.
- ▪Attackers accessed data from approximately 3,800 internal repositories through a compromised VS Code extension.
- ▪The breach was not due to a zero-day vulnerability in GitHub's servers but rather a malicious extension on an employee's laptop.
- ▪Developers are encouraged to avoid hardcoding API keys and to store sensitive information securely.
DEV.to (Top) files mainly under programming. We currently carry 4,924 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 | DEV.to (Top) |
| Canonical URL | https://dev.to/yusuf_khalidd/hmy-mftyh-api-mn-df-vs-code-dr-386n |
| Publication time | Thu, 21 May 2026 02:40:06 +0000 |
| Retrieval time | 2026-05-21T03:05:03.342Z |
| Last seen | 2026-05-21T03:05:03.342Z |
| 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 | None |
| Cluster logic | Not yet clustered, or no peer story found in the clustering window. |
| 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
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3821724) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Yusuf Khalidd Posted on May 21 • Originally published at apidog.com حماية مفاتيح API من إضافة VS Code ضارة #api #github #security #vscode في 20 مايو 2026، أكدت GitHub أن مهاجمين سرقوا بيانات من حوالي 3800 مستودع شيفرة داخلي. لم تكن نقطة الدخول ثغرة يوم-صفر في خوادم GitHub، بل إضافة VS Code مخترقة مثبتة على حاسوب محمول لموظف واحد. عندما تعمل الإضافة بصلاحيات المطور نفسها، يمكنها قراءة الشيفرة، ملفات التهيئة، وبيانات الاعتماد الموجودة في مساحة العمل.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
