←
Miguel Balparda10,299 posts
Miguel Balparda avatar

Miguel Balparda

@mbalparda

I like computers.

◷ Joined October 2010▧ 1,102 Photos and videos
Miguel Balparda avatar
Miguel Balparda@mbalparda·Oct 6

A bit late to the party, but I've been named an @AdobeCommerce Champion for the 2026-2027 class! I have been in this community since the #Magento 1 days: core maintainer, more than 300 merged PRs, and tons of events run almost entirely by volunteers. The platform has changed names a couple of times since then. The people mostly have not. Congratulations to everyone else in the class, across Commerce, Analytics, AEM, Experience Platform, Marketo Engage and Workfront. And thank you to the community itself. Nearly everything I know about commerce, I learned from people in it giving their work away for free.

Post attachment
Miguel Balparda avatar
Miguel Balparda@mbalparda·Nov 11

A lot has changed since I was last here. One thing hasn’t: let someone else manage your servers so you can focus on what merchants care about the most: selling. Wanna talk? My DMs are open! lnkd.in/p/dgC_WEX2

Miguel Balparda avatar
Miguel Balparda@mbalparda·Nov 3

For my next act, I'm going back to where it all started. I'm rejoining @Nexcess as Senior Product Manager for @AdobeCommerce and #magento2. Tired of babysitting servers? My DMs are open!

Nexcess Digital Cloud gives agencies a managed hosting foundation for growing client portfolios, bringing WordPress, WooCommerce, and Magento sites together under one account with expert support. With managed migrations, security protections, automatic scaling, and volume pricing, Nexcess helps teams spend less time managing infrastructure and more time building client experiences that perform. In this episode, we speak with Miguel Balparda, Senior Product Manager at @Nexcess, about what managed hosting means when a serious security incident threatens live ecommerce stores. Drawing on his experience as a Magento community maintainer and Adobe Commerce Champion, Balparda takes us behind the scenes of Nexcess’s response to the Style Smuggler vulnerability affecting Magento and Adobe Commerce. He explains how suspicious GraphQL requests, recurring file signatures, malware scans, and information from security researchers helped the team identify a coordinated attack. The discussion shows why protecting merchants requires both a deep understanding of the application and the ability to act quickly while keeping storefronts operational and customer payment information safe. The conversation explores the difficult tradeoffs between containing an attack and preserving the functionality merchants need to process orders. Balparda explains why temporarily blocking GraphQL traffic reduced exposure but also disrupted some storefronts, prompting the team to refine its response as patches became available. He walks through the challenges of evaluating environments across different Magento versions, server configurations, and third-party extensions, and describes how Nexcess adapted security patches for older, unsupported versions. He also shares how AI helped accelerate that backporting work, while emphasizing the continued need for experienced engineers, compatibility testing, and checks on site stability. Clear communication is another central theme: merchants need to understand what their provider changed, what remains their responsibility, and why emergency patches applied directly to production must also be incorporated into their own codebase so a future deployment does not undo the protection. The episode also examines the limits of automation and the shared responsibilities involved in running a customizable ecommerce platform. Balparda discusses why heavily modified stores are difficult to patch consistently, how better-vetted extensions and more standardized environments could make maintenance easier, and why some merchants continue to choose Magento for its flexibility and control. He explains where hosting support can help and where a merchant’s developers or agency must take over, then offers practical questions for evaluating a provider’s application expertise, troubleshooting capabilities, and involvement in the broader ecosystem. His broader message is that managed hosting depends on knowledgeable people, layered defenses, transparent communication, and ongoing collaboration. By investing in security before an incident occurs, merchants can better protect their customers, reduce disruption, and avoid more costly problems down the road.

43:45
SourceForge avatar
⟳ Miguel Balparda retweeted
SourceForge@sourceforge·Nov 3

Nexcess Digital Cloud gives agencies a managed hosting foundation for growing client portfolios, bringing WordPress, WooCommerce, and Magento sites together under one account with expert support. With managed migrations, security protections, automatic scaling, and volume pricing, Nexcess helps teams spend less time managing infrastructure and more time building client experiences that perform. In this episode, we speak with Miguel Balparda, Senior Product Manager at @Nexcess, about what managed hosting means when a serious security incident threatens live ecommerce stores. Drawing on his experience as a Magento community maintainer and Adobe Commerce Champion, Balparda takes us behind the scenes of Nexcess’s response to the Style Smuggler vulnerability affecting Magento and Adobe Commerce. He explains how suspicious GraphQL requests, recurring file signatures, malware scans, and information from security researchers helped the team identify a coordinated attack. The discussion shows why protecting merchants requires both a deep understanding of the application and the ability to act quickly while keeping storefronts operational and customer payment information safe. The conversation explores the difficult tradeoffs between containing an attack and preserving the functionality merchants need to process orders. Balparda explains why temporarily blocking GraphQL traffic reduced exposure but also disrupted some storefronts, prompting the team to refine its response as patches became available. He walks through the challenges of evaluating environments across different Magento versions, server configurations, and third-party extensions, and describes how Nexcess adapted security patches for older, unsupported versions. He also shares how AI helped accelerate that backporting work, while emphasizing the continued need for experienced engineers, compatibility testing, and checks on site stability. Clear communication is another central theme: merchants need to understand what their provider changed, what remains their responsibility, and why emergency patches applied directly to production must also be incorporated into their own codebase so a future deployment does not undo the protection. The episode also examines the limits of automation and the shared responsibilities involved in running a customizable ecommerce platform. Balparda discusses why heavily modified stores are difficult to patch consistently, how better-vetted extensions and more standardized environments could make maintenance easier, and why some merchants continue to choose Magento for its flexibility and control. He explains where hosting support can help and where a merchant’s developers or agency must take over, then offers practical questions for evaluating a provider’s application expertise, troubleshooting capabilities, and involvement in the broader ecosystem. His broader message is that managed hosting depends on knowledgeable people, layered defenses, transparent communication, and ongoing collaboration. By investing in security before an incident occurs, merchants can better protect their customers, reduce disruption, and avoid more costly problems down the road.

43:45
Matthew Prince 🌥 avatar
⟳ Miguel Balparda retweeted
Matthew Prince 🌥@eastdakota·Oct 21

Two classes extremely bad cyber vulnerabilities disclosed in the last 24 hours. The first potentially impacts everyone online. The second impacts nearly everyone running a server. tl;dr: Everyone should upgrade their OS and Browser as soon as possible. If you run a server you should upgrade PHP (or ensure it’s removed if you’re not using it) as soon as possible. The first class of vulnerabilities is a set of root TLS certificates that were discovered to have a trivial private key. Literally the number 4. These roots were controlled by #eMudhra. The problem is that with that an attacker could create a certificate and, if they could get in the traffic flow, intercept traffic to any site or service. The solution is to stop trusting certificates issued by these vulnerable roots. Upgrading your browser and OS is the fastest way for most Internet users to do this. The second class of vulnerabilities doesn’t apply to most consumers directly, but does apply to most anyone running a server. These vulnerabilities have been dubbed #php2shell. PHP is one of the most widely used web programming languages. It’s estimated 70% of websites run on PHP. These vulnerabilities allow an attacker to send a crafted set of queries to a server running PHP and potentially take over the server. From there they could potentially read, modify, delete, or repurpose anything on the server. The solution is to upgrade PHP to the latest version ASAP. Even if you’re not using PHP for your web development, it’s often included by default. So make sure it is either upgraded or fully removed. @Cloudflare received advanced warning of both of these classes of vulnerabilities. We’ve ensured that where we act as a proxy we are no longer trusting the vulnerable roots. We are also reviewing certificate transparency (CT) logs for any sign the vulnerability was exploited before its disclosure. We have not found any evidence but CT logs are not perfect and a sophisticated attacker who knew about the weakness could have exploited it without a new certificate being logged. For the PHP vulnerabilities, we have deployed mitigations available for all customers for free. Because of the complexity of the vulnerabilities and number of ways it can be exploited, we also released new WAF capabilities that are unique in the industry to catch the exploit based on the response. These too are available for every Cloudflare customer for free. Even if you are taking advantage of Cloudflare’s protection, it is important to upgrade your OS, browsers, and PHP installations as soon as possible. We can provide a strong bandaid, but the best protection is to fix the underlying problem. If you’re interested in learning more, you can read our blogs: Vulnerable roots: blog.cloudflare.com/emudhra-… PHP vulnerabilities: blog.cloudflare.com/php-vuln…

SportsCenter avatar
⟳ Miguel Balparda retweeted
SportsCenter@SC_ESPN·Aug 29

🇦🇷🏆 ¡¡SON HISTORIA PURA!! ¡SOFI CAIRO MARCÓ SU PENAL Y LAS LEONAS SON CAMPEONAS DEL MUNDO POR TERCERA VEZ EN SU HISTORIA! ¡LA TERCERA ESTRELLA LLEGÓ PARA EL HOCKEY FEMENINO! 🇦🇷🏆 📺 Todos los partidos de #HWC2026 en Disney+ Plan Premium

Post attachment
Tobias_Petry.sql avatar
⟳ Miguel Balparda retweeted
Tobias_Petry.sql@tobias_petry·Jul 26

Didn't expect to learn something new about DNS... But I did! This new record type has been standardized in 2023. Completely missed that. And its already used: Cloudflare automatically adds it to indicate http2 and http3 support with the available ip adresses

Post attachment

A HTTPS record will prevent the browser from ever dialing :80, your domain doesn't need ot be on the HSTS preload list hardcoded into browsers. Quite cool!

Erling Haaland avatar
⟳ Miguel Balparda retweeted
Erling Haaland@Erling·Jul 25

Yes... I saw all the memes. Now time to react! 👀🤣 Full episode on YT! 🎬

0:24
Sudanalytics avatar
⟳ Miguel Balparda retweeted
Sudanalytics@sudanalytics_·Jul 16

“HO VISTO MARADONA”. ASÍ SE FESTEJA EN NÁPOLES. 🤯🇮🇹🇦🇷

0:28
Guillermo Rauch avatar
⟳ Miguel Balparda retweeted
Guillermo Rauch@rauchg·Jul 1

WordPress on @vercel Fluid with Active CPU from a single 𝙳𝚘𝚌𝚔𝚎𝚛𝚏𝚒𝚕𝚎.𝚟𝚎𝚛𝚌𝚎𝚕. MySQL on @planetscale. 30s deployments incl. "𝚍𝚘𝚌𝚔𝚎𝚛 𝚋𝚞𝚒𝚕𝚍" in the cloud. Just one command: 𝚗̶𝚘̶𝚠̶ 𝚟𝚎𝚛𝚌𝚎𝚕.

Post attachment
Chris Tate avatar
⟳ Miguel Balparda retweeted
Chris Tate@ctatedev·Jul 1

Vercel Ship (so far) ▲ Vercel Services — Run full stack on Vercel — Microservices on Vercel — Private service comms ▲ eve — The framework for building agents — Durable agents with one folder — Sandboxing, approvals and evals ▲ WebSocket support — Persistent connections ▲ Vercel Functions — Dockerfile support — 5 GB packages, 30 min — Zero-config Node servers ▲ Vercel Agent in Dashboard — Autonomous investigations — Plan-based permissions — Fixes surfaced as PRs ▲ Vercel Container Registry — Container images on Vercel — OCI push, pull and tag ▲ Vercel Sandbox — Custom images — Persistent sandbox storage — 24 hour runtime + expiration ▲ AI SDK 7 + agent harnesses — Toolkit for building agents — Coding-agent harnesses ▲ Chat SDK — Multi-channel agents ▲ Access & security — Vercel Passport: OIDC access — Vercel Connect: external services — OIDC audiences + Audit Logs ▲ Enterprise apps and agents — Security posture dashboard — Vercel Functions in your cloud ▲ AI Gateway — Voice, speech and transcription — API key budgets ▲ Vercel Blob — Private blob storage — Signed URLs and OIDC auth ▲ Builds & deployments — 500 concurrent builds for Pro — Vercel Drop — Elastic builds ▲ Vercel CLI — Speed Insights + Web Analytics — Trace any request — Deployment limits removed ▲ Observability — Trace eve sessions — Trace Workflow runs ▲ Workflows — Inflight cancellation — Nitro v3 + TanStack Start ▲ SDK-free Vercel Flags — No SDK keys

Guillermo Rauch avatar
⟳ Miguel Balparda retweeted
Guillermo Rauch@rauchg·Apr 19

Here's my update to the broader community about the ongoing incident investigation. I want to give you the rundown of the situation directly. A Vercel employee got compromised via the breach of an AI platform customer called Context.ai that he was using. The details are being fully investigated. Through a series of maneuvers that escalated from our colleague’s compromised Vercel Google Workspace account, the attacker got further access to Vercel environments. Vercel stores all customer environment variables fully encrypted at rest. We have numerous defense-in-depth mechanisms to protect core systems and customer data. We do have a capability however to designate environment variables as “non-sensitive”. Unfortunately, the attacker got further access through their enumeration. We believe the attacking group to be highly sophisticated and, I strongly suspect, significantly accelerated by AI. They moved with surprising velocity and in-depth understanding of Vercel. At the moment, we believe the number of customers with security impact to be quite limited. We’ve reached out with utmost priority to the ones we have concerns about. All of our focus right now is on investigation, communication to customers, enhancement of security measures, and sanitization of our environments. We’ve deployed extensive protection measures and monitoring. We’ve analyzed our supply chain, ensuring Next.js, Turbopack, and our many open source projects remain safe for our community. The recommendation for all Vercel customers is to follow the Security Bulletin closely (vercel.com/kb/bulletin/verce…). My advice to everyone is to follow the best practices of security response: secret rotation, monitoring access to your Vercel environments and linked services, and ensuring the proper use of the sensitive env variables feature. In response to this, and to aid in the improvement of all of our customers’ security postures, we’ve already rolled out new capabilities in the dashboard, including an overview page of environment variables, and a better user interface for sensitive env var creation and management. As always, I’m totally open to your feedback. We’re working with elite cybersecurity firms, industry peers, and law enforcement. We’ve reached out to Context to assist in understanding the full scale of the incident, in an effort to protect other organizations and the broader internet. I also want to thank the Google Mandiant team for their active engagement and assistance. It’s my mission to turn this attack into the most formidable security response imaginable. It’s always been a top priority for me. Vercel employs some of the most dedicated security researchers and security-minded engineers in the world. I commit to keeping you updated and rolling out extensive improvements and defenses so you, our customers and community, can have the peace of mind that Vercel always has your back.

Brendan Falk avatar
⟳ Miguel Balparda retweeted
Brendan Falk@BrendanFalk·Apr 19

To check if your Google Workspace has been compromised by the same tool that compromised Vercel: 1. Go to admin.google.com/ac/owl/list… - This is Google Admin Console > Security > Access and Data Control > API Controls > Manage app access > Accessed Apps 2. Filter by ID = 110671459871-30f1spbu0hptbs6… - This is the ID of the compromised OAuth app If you see an app after filtering, you have potentially been compromised

Post attachment
Jaime Blasco avatar
⟳ Miguel Balparda retweeted
Jaime Blasco@jaimeblascob·Apr 19

Google has deleted the account but I’m confident the third party AI tool that vercel mentioned in the blog post is context[.]ai based on a now removed chrome browser extension listing linked to an oauth grant in the same account id

Security incident involving Vercel. Check for the following Oauth grant in your environment http://110671459871-30f1spbu0hptbs60cb4vsmv79i7bbvqj.apps.googleusercontent[.]com