<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: AJ</title>
    <description>The latest articles on DEV Community by AJ (@anne_jacobs_ac166227aa92b).</description>
    <link>https://dev.to/anne_jacobs_ac166227aa92b</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3959154%2F28c0e805-d2a9-49b9-8b01-6af8e6a4b782.jpeg</url>
      <title>DEV Community: AJ</title>
      <link>https://dev.to/anne_jacobs_ac166227aa92b</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/anne_jacobs_ac166227aa92b"/>
    <language>en</language>
    <item>
      <title>Why Third-Party Scripts Are Still the Weakest Link in Modern Web Stacks</title>
      <dc:creator>AJ</dc:creator>
      <pubDate>Fri, 06 Nov 2026 01:29:15 +0000</pubDate>
      <link>https://dev.to/anne_jacobs_ac166227aa92b/why-third-party-scripts-are-still-the-weakest-link-in-modern-web-stacks-4772</link>
      <guid>https://dev.to/anne_jacobs_ac166227aa92b/why-third-party-scripts-are-still-the-weakest-link-in-modern-web-stacks-4772</guid>
      <description>&lt;p&gt;Every modern web application is built on an uncomfortable foundation of unearned trust.&lt;/p&gt;

&lt;p&gt;Engineering teams spend months locking down backend infrastructure, setting up strict database firewalls, enforcing encrypted server channels, and putting code through rigorous multi-stage reviews. Then, right before launching to production, a product manager or marketing lead asks to track user analytics, monitor page-load speeds, or embed a customer support chat widget.&lt;/p&gt;

&lt;p&gt;Within minutes, a few small script tags are added to the website. Just like that, external code from half a dozen outside companies is invited directly into the browser runtime of every logged-in user. And when one of those external companies gets compromised, no server-side security team on Earth can stop the damage.&lt;/p&gt;

&lt;p&gt;The recent exploit on &lt;strong&gt;Polymarket&lt;/strong&gt; — where a hijacked performance-monitoring vendor silently drained over &lt;strong&gt;$2.7 million from active user accounts&lt;/strong&gt; in under an hour—is a stark wake-up call. It proves that client-side supply-chain attacks aren't theoretical. More importantly, it exposes how standard web architecture routinely makes these breaches disastrously easy.&lt;/p&gt;

&lt;h2&gt;
  
  
  &lt;strong&gt;The Anatomy of the Attack: What Actually Happened?&lt;/strong&gt;
&lt;/h2&gt;

&lt;p&gt;The Polymarket breach wasn't caused by a flaw in the platform's core product, a database leak, or a broken smart contract. The company's internal servers were never actually hacked.&lt;/p&gt;

&lt;p&gt;Instead, attackers targeted an external vendor named &lt;strong&gt;DebugBear&lt;/strong&gt;, a third-party tool used to track website speed. By taking control of the vendor's distribution domain through a domain-name compromise, the attackers swapped out the vendor's legitimate monitoring file for a malicious one. Because Polymarket's website was set up to fetch and run that vendor file live on pages where users traded, the injected code executed automatically inside active browser sessions.&lt;/p&gt;

&lt;p&gt;The malicious file didn't need to guess passwords or break encryption key pairs. It simply loaded into the same overall browser space as the rest of the application. Once inside, it quietly:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;1. Read active user session data&lt;/strong&gt; straight out of the browser's local memory.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. Accessed the platform's internal transaction tools&lt;/strong&gt; already running on the open page.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3. Initiated unauthorized money transfers&lt;/strong&gt; to attacker wallets using valid, live session tokens.&lt;/p&gt;

&lt;p&gt;To the receiving servers and verification networks, every single request looked completely legitimate—because it was generated by an authenticated, active user session.&lt;/p&gt;

&lt;h2&gt;
  
  
  &lt;strong&gt;Why Standard Security Defense Controls Fail&lt;/strong&gt;
&lt;/h2&gt;

&lt;p&gt;When news of a breach breaks, non-security teams often ask, "Don't we have web firewalls and security filters to catch this?" In the modern client-side environment, traditional defenses fall short for three key reasons:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;1. Security Rules Check Origins, Not Behaviors&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Most web security policies rely on allowlists. Teams define a rule that says: "Trust any file delivered from this specific vendor web address." When attackers took over the vendor's domain, the web address didn't change—only the content stored on it did. The user's web browser checked its allowlist, verified that the web address was on the approved list, and ran the malicious file without hesitation. Allowing an address only verifies where a file comes from, not what it does once it arrives.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. Backend Security Systems Are Blind to the Browser&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Firewalls and server scanners inspect incoming traffic heading directly to your own servers. Automated testing scanners evaluate code that your own developers write. Neither of those tools can see or analyze an external script fetched directly by an end user's browser from an entirely different company's server.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3. Browsers Suffer from an All-Access Design&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;By default, web browsers do not separate permissions for different scripts on the same webpage. If your core banking app and a lightweight page-speed tracker run on the same screen, they share the exact same house key. The tracker has full visibility into user input, browser storage, and active buttons on the page. Adding a third-party widget to a financial dashboard is the architectural equivalent of handing your building manager the master key to your personal safe.&lt;/p&gt;

&lt;h2&gt;
  
  
  &lt;strong&gt;Architectural Solutions: Securing the Client Side&lt;/strong&gt;
&lt;/h2&gt;

&lt;p&gt;If web development is going to move past these recurring supply-chain vulnerabilities, engineering teams must stop viewing third-party code as harmless add-ons and start treating it as untrusted software.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;1. Require File Verification Hashes&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;If an application must load files hosted by external vendors, it should enforce cryptographic hash checking. By storing a digital signature of the vendor file on your own servers, the user's browser can verify that the fetched file matches the expected pattern. If an attacker tampers with the vendor file on their domain, the signatures won't match, and the browser blocks execution.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. Sandbox Outside Code Off the Main Thread&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Analytics and chat widgets almost never need direct access to the main visual surface or internal data store of an app. Running third-party tools inside isolated background workers isolates them completely from sensitive browser memory, stored login details, and payment buttons.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3. Self-Host External Dependencies&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Rather than pointing websites to live external URLs that can change at a moment's notice, development teams should download, audit, and host third-party files on their own secure infrastructure. Bringing third-party code under internal deployment pipelines ensures that outside updates cannot go live without automated safety checks and manual approval.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4. Isolate Sensitive Session Storage&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Critical authentication tokens and payment actions should never sit in general browser storage where any script on the page can freely read them. Storing key credentials inside locked-down, restricted-access browser containers prevents rogue scripts from harvesting user access even if they manage to breach the page.&lt;/p&gt;

&lt;h2&gt;
  
  
  &lt;strong&gt;The Big Takeaway for Product Teams&lt;/strong&gt;
&lt;/h2&gt;

&lt;p&gt;Client-side supply-chain attacks succeed because web creators treat external scripts like plug-and-play features rather than full software installations running inside active customer accounts.&lt;/p&gt;

&lt;p&gt;The next time a team considers dropping a quick analytics snippet or marketing pixel onto a secure dashboard, the fundamental question shouldn't be "How fast can we set this up?" It needs to be: "If this vendor gets compromised tomorrow, what can their code do to our users?" If the answer is "anything it wants," the software design must change.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Sources &amp;amp; Further Reading:&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;SecurityWeek&lt;/strong&gt;: Polymarket Returns $3.9 Million to Traders as DebugBear Cites DNS Hijack   &lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Reflectiz Threat Research&lt;/strong&gt;: Polymarket Hack: DebugBear Script Drained $2.7M   &lt;/p&gt;

&lt;p&gt;&lt;strong&gt;InfoStealers / Hudson Rock:&lt;/strong&gt; Polymarket Breach Alert: Wallet-Draining Code Found in a Third-Party Script   &lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Halborn Security Analysis&lt;/strong&gt;: Explained: The Polymarket Hack (June 2026 Context)   &lt;/p&gt;

</description>
      <category>webdev</category>
      <category>security</category>
      <category>architecture</category>
      <category>javascript</category>
    </item>
    <item>
      <title>How We Let Silicon Valley Steal the Future (And How Developers Can Take It Back)</title>
      <dc:creator>AJ</dc:creator>
      <pubDate>Mon, 26 Oct 2026 22:08:36 +0000</pubDate>
      <link>https://dev.to/anne_jacobs_ac166227aa92b/how-we-let-silicon-valley-steal-the-future-and-how-developers-can-take-it-back-2ie0</link>
      <guid>https://dev.to/anne_jacobs_ac166227aa92b/how-we-let-silicon-valley-steal-the-future-and-how-developers-can-take-it-back-2ie0</guid>
      <description>&lt;p&gt;Remember when the tech industry’s pitch was about abundance, open collaboration, and empowering the individual? Somewhere along the way, the garage-startup ethos traded its idealism for consolidation, walled gardens, and centralized control.&lt;/p&gt;

&lt;p&gt;The conversation around how tech lost its way—echoed in recent cultural critiques examining Silicon Valley's shifting ambitions—forces us to look inward. As software engineers, indie hackers, and open-source maintainers, we built the tools of the modern world. But we also stood by while the definition of "innovation" was hijacked by corporate monopolies and algorithmic rent-seekers.&lt;/p&gt;

&lt;p&gt;Here is a look at how we got here, why the tech narrative stalled, and what we can do to write a different next chapter.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;1. From "Don't Be Evil" to Rent Extraction&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;In the early days, the web felt expansive. The underlying premise of software development was leverage: write a script once, share a library, and empower thousands of people to do things they couldn't do yesterday.&lt;/p&gt;

&lt;p&gt;Over the last decade, however, the incentive structure shifted radically. Venture capital-backed growth stopped prioritizing raw utility and started focusing on monopolistic capture.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;APIs closed up&lt;/strong&gt;: Free, open endpoints became locked behind enterprise paywalls.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Open Source was commercialized&lt;/strong&gt;: Community-driven repositories increasingly became loss-leaders or training grounds for proprietary foundational models.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The "Enshittification" cycle&lt;/strong&gt;: Platforms courted users, locked in developers, and then squeezed both to maximize extraction for shareholders.&lt;/p&gt;

&lt;p&gt;Instead of building tools that expand human capability, a massive chunk of modern engineering brainpower is currently locked into ad-tech optimization, hyper-targeted surveillance, and proprietary silos designed to keep users trapped inside a single ecosystem.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. The AI Gold Rush and the Illusion of Progress&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;We are currently living through an unprecedented acceleration in artificial intelligence, yet it often feels culturally stagnant. Why? Because the prevailing narrative treats AI not as an amplifier of human creativity, but as a replacement mechanism—a way to cut labor costs, saturate the internet with synthetic content, and centralize power among a tiny handful of cloud oligopolies.&lt;/p&gt;

&lt;p&gt;When tech leadership measures "progress" purely in parameters, compute scale, and market capitalization rather than societal flourishing, we stop building a future that people actually want to live in. We get incremental wrapper apps instead of systemic solutions to hard problems like climate resilience, education equity, and decentralized infrastructure.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3. Reclaiming the Developer Ethos&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The good news is that tech isn't monolithic, and the future hasn't been permanently foreclosed—it's just being heavily contested. If we want to course-correct, developers need to consciously shift how and what we build:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Support True Open Source&lt;/strong&gt;: Shift from passive consumption to active contribution. Defend licenses that protect user freedom and resist corporate capture of foundational software layers.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Build Locally, Interoperate Globally&lt;/strong&gt;: Reject walled gardens. Favor protocols over platforms (think ActivityPub, local-first software, and self-hosted alternatives).&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Question the Product&lt;/strong&gt;: Next time you're assigned a ticket, ask: Does this actually make someone’s life better, or is it just optimizing an engagement loop?&lt;/p&gt;

&lt;p&gt;Silicon Valley didn't steal the future in a single hostile takeover; it happened one compromised architectural decision, one closed API, and one traded ideal at a time. But code is malleable. The culture of software is written by the people typing the lines—which means we still have the power to refactor it.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;em&gt;What are you building to push back against the walled gardens? Let’s talk in the comments.&lt;/em&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;📚 &lt;strong&gt;Source &amp;amp; Further Reading&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Primary Inspiration&lt;/strong&gt;: How Silicon Valley Stole the Future — The New York Times Magazine (October 2026). A sharp examination of how tech's cultural and economic ambitions shifted from broad technological optimism to centralized corporate control.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Further Exploration&lt;/strong&gt;:&lt;/p&gt;

&lt;p&gt;Cory Doctorow’s ongoing essays on Enshittification and platform decay.&lt;/p&gt;

&lt;p&gt;The Local-First Software Manifesto — Rethinking software architecture to prioritize user ownership, privacy, and offline capabilities.&lt;/p&gt;

&lt;p&gt;The IndieWeb Movement — A community-driven effort to return to an independent, interconnected web owned by creators rather than platforms.&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>ai</category>
      <category>opensource</category>
      <category>programming</category>
    </item>
    <item>
      <title>Anthropic wants to fund the public. Musk wants to hand over shares. Which is better?</title>
      <dc:creator>AJ</dc:creator>
      <pubDate>Thu, 22 Oct 2026 21:50:27 +0000</pubDate>
      <link>https://dev.to/anne_jacobs_ac166227aa92b/anthropic-wants-to-fund-the-public-musk-wants-to-hand-over-shares-which-is-better-26gj</link>
      <guid>https://dev.to/anne_jacobs_ac166227aa92b/anthropic-wants-to-fund-the-public-musk-wants-to-hand-over-shares-which-is-better-26gj</guid>
      <description>&lt;p&gt;&lt;strong&gt;Two announcements landed within a day of each other this week, and I can’t stop thinking about them as a developer.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Anthropic said on Sunday that it would commit 5% of its shares to a new “public benefit” fund. Musk then replied that the shares should go directly to the public, and on Monday he pledged to give every American child one share of SpaceX next year. The fund could support charities or make direct payments to specific groups, including workers whose jobs are disrupted by AI. Anthropic also says it has already committed $200m to studying and addressing the technology’s impact on employment. &lt;br&gt;
Musk vows a SpaceX share for every US child next year, says it's 'the first of many'&lt;br&gt;
 +2&lt;/p&gt;

&lt;p&gt;&lt;em&gt;&lt;strong&gt;Disclosure&lt;/strong&gt;: I’m writing this with help from Claude, which Anthropic makes. I’m not neutral, so please push back hard.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Why the timing matters&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;A new AP-NORC poll found that 64% of Americans think AI is developing “too fast,” while only 8% say it’s moving too slowly. Whatever the motives, both announcements read as responses to that mood. We build the tools people are nervous about, so we should have an opinion. &lt;br&gt;
nbcmontana&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The case for Anthropic’s approach&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;A fund can be designed. It can target people who lose work to automation instead of spreading value evenly, and it can pay for retraining or research that a one-time share handout never would. Unlike Musk’s proposal, it would hold company equity to finance public benefit projects rather than distribute shares directly to individuals. That could give it staying power and let it adapt as we learn where the damage actually lands. &lt;br&gt;
cityam&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The case for Musk’s approach&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Direct distribution is simple and hard to game. No board decides who counts as “affected,” and no administrator takes a cut. A child holding a share has a literal stake in how the industry performs. The weak points are scale and shape: one share is a symbolic amount for most families, and it isn’t aimed at anyone in particular.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Where I’m skeptical of both&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Governance. Who decides how the fund spends its money? A fund inside the company that created it raises obvious questions about independence.&lt;br&gt;
Scale versus the problem. If AI displaces work at the scale some leaders warn about, is 5% of equity enough? Is one share per kid?&lt;br&gt;
Timing. Anthropic is planning a major IPO as soon as November, and SpaceX only recently went public. Pledges that arrive near a big liquidity event deserve scrutiny, whoever makes them. &lt;br&gt;
nbcmontana&lt;br&gt;
Substitution. Does a generous-looking gift reduce pressure for policy, such as worker protections, transparency rules, or safety standards?&lt;br&gt;
What I’d like to hear from you&lt;br&gt;
Would you rather have a targeted fund or direct shares? Or neither, with the money going to something else entirely?&lt;br&gt;
If you work in a field exposed to automation, what would actually help you: cash, retraining, or something else?&lt;br&gt;
What governance structure would make you trust a fund like this? Independent trustees? Public reporting? Something else?&lt;br&gt;
Are pledges like these a sign the industry is taking its responsibility seriously, or mostly PR ahead of an IPO? Both can be true.&lt;br&gt;
Is “give shares to the public” a model other AI companies should copy, or does it distract from regulation?&lt;/p&gt;

&lt;p&gt;&lt;em&gt;&lt;strong&gt;I don’t have a settled view and I’d rather hear from people who build this stuff every day. Tell me where I’m wrong in the comments.&lt;/strong&gt;&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>discuss</category>
      <category>career</category>
      <category>opensource</category>
    </item>
  </channel>
</rss>
