Forward Deployed Engineer

Australia arrests alleged TeamPCP hackers in supply-chain attack case. Post Views: 7 Australia authorities have detained two individuals suspected of involvement in the TeamPCP cybercriminal network, which orchestrated widespread supply-chain attacks targeting software development ecosystems. Arrest of suspects in TeamPCP network. Australia authorities have detained two individuals suspected of involvement in the TeamPCP cybercriminal network, which orchestrated widespread supply-chain attacks targeting software development ecosystems. The suspects, aged 21 and 23, were apprehended in Western Australia on August 26, 2026, following an investigation into malicious activities that compromised open-source software repositories and developer infrastructure. Impact of TeamPCP attacks. TeamPCP has been linked to multiple high-profile breaches affecting projects such as Trivy, LiteLLM, Telnyx, SAP, and TanStack, as well as infiltrations of the European Commission, Mistral AI, OpenAI, and GitHub. The group's operations involved inserting malicious code into open-source projects hosted on public repositories, which developers subsequently integrated into their applications. This method enabled the exfiltration of authentication credentials, source code, and sensitive data from systems used by government agencies, academic institutions, and private enterprises. According to the Australian Federal Police (AFP) and FBI, the malicious code distributed by TeamPCP impacted over 1,000 organizations globally, resulting in the theft of 500,000 credentials and the unauthorized transfer of at least 300GB of data. Investigation and evidence collection. The investigation commenced in April 2026 after cybersecurity firms provided critical intelligence to law enforcement. During the operation, authorities seized electronic devices and digital evidence for forensic analysis. The suspects are alleged to have received cryptocurrency payments for their roles in the attacks. Independent analyses by Flare and Brian Krebs highlighted connections between Telegram activity, reused usernames, and other digital footprints that helped identify the individuals. Charges and legal consequences. The two detainees face 14 combined charges related to unauthorized data access, data modification, and facilitating criminal activities. The younger suspect also faces allegations of handling $100,000 in illicit funds and failing to comply with data access requirements. Each charge carries potential sentences of 3 to 20 years in prison. The AFP stated that additional arrests or charges remain possible as investigators review seized materials. Implications for software supply chain security. The case underscores the vulnerabilities in software supply chains, with research indicating that 37% of attacker activities go undetected even after gaining valid credentials. The incident has prompted renewed scrutiny of open-source security practices and the need for enhanced monitoring of developer platforms.

RCS agent registration API: why agencies should wait. Telnyx turned RCS agent registration into two API calls. The stage that decides whether your messages land is still a human queue. What agencies should do. Zach Brick · Founder & CEO, iBluSend · August 26, 2026 Telnyx shipped the easy half of RCS. Two API calls now stand between an agency and a registered RCS brand. The stage that decides whether a single message reaches a human is still a queue with telco employees sitting in it. Telnyx published its RCS agent registration API release note, and the shape is clean: register the brand, register the agent, move through a two-stage flow from brand verification to carrier launch, with status tracking across the whole thing. Work that used to live in a spreadsheet and an email thread now fires from your onboarding script. That is genuinely good engineering, and I'd rather have it than not. But the most revealing line in that release note isn't the registration call at all. It's the status tracking, and what it quietly concedes about stage two. iBluSend'll get to that, because it's the part that should change your Q4 plan. What did the RCS agent registration API actually automate? The submission, not the approval. Brand verification and agent creation become API calls with a status you can poll. Carrier launch approval stays exactly where it always sat: with mobile network operators reviewing your agent on their own timeline. Telnyx automated the form. Nobody automated the reviewer. That distinction matters more than it sounds. Every RCS pitch of the last two years has treated registration friction as the reason adoption stalled, as if the only thing standing between agencies and rich branded messaging was a tedious intake process. Remove the intake process and you find out whether that was true. Spoiler from the release note itself: it advertises a flow that runs "through carrier launch," which is a polite way of saying the flow does not end when you get a 200 back. It ends when someone at a carrier says yes. Why is everyone reading this as "RCS is finally easy"? Because the visible friction disappeared, and visible friction is what people measure. An agency owner who spent three weeks last year assembling brand documents reads "two API calls" and feels the relief in their spine. That reaction is honest. It's also measuring the wrong thing. The industry has a habit here. Every time a channel's paperwork gets automated, the trade press declares the channel unlocked, and then everyone rediscovers that paperwork was never the bottleneck. 10DLC went through this exact arc: providers built slick registration wizards, agencies registered in an afternoon, and then spent the following year discovering that carrier filtering, throughput tiers and campaign vetting were the real gates. The wizard was lovely. The messages still got filtered. RCS is running the same play. Registration got fast. Delivery approval didn't move. What happens during carrier launch approval? Your verified agent has to be launched by each carrier that will carry its traffic, and carriers make that decision individually, on their own review cadence, with their own criteria. Until that happens, your beautifully registered agent sends to nobody on that network. Which brings iBluSend back to the status tracking, the detail I told you to hold onto. Think about what a status endpoint is for. You expose one when the underlying process is slow enough and opaque enough that the caller needs a way to check on it. Nobody builds status polling for something that returns instantly. The presence of that endpoint is Telnyx being straight with you: the second stage takes long enough that you'll want to watch it. So the honest read of this release is that RCS registration became an API, and RCS launch became an API-shaped waiting room. You've traded a slow form for a fast form plus a refresh button. That's an improvement in developer experience. It is not an improvement in time-to-first-reply. Who actually wins when RCS registration becomes an API call? Here's the flip. Everyone is covering this as a win for agencies. Ask who else gets the same API, and it reads very differently. Your competitor's agency gets it. So does the one down the street with worse copy and a bigger list. Registration was never a moat, but it was at least a filter: a process annoying enough that plenty of shops never finished it. Remove the annoyance and the filter goes with it. A capability every competitor can acquire in a sprint is not an advantage, it's a baseline, and baselines cost money to maintain while returning nothing in differentiation. There's a second-order effect worth pricing in too. When registration is cheap, agent volume goes up, and when agent volume goes up, carriers get stricter about what they launch and what they filter, because that's the only lever they have left. Easy registration tends to produce harder delivery over time. The channel gets more crowded before it gets more effective, and the agencies who planned their quarter around a launch date they don't control absorb that timing risk personally. Where does that leave iMessage and GoHighLevel outreach? Exactly where it was, which is the point. The differentiator moves back to the lane nobody can request access to through an API: the blue bubble on an iPhone, sent from a real Mac, with read receipts and typing indicators the recipient already trusts because their friends produce the same artifacts. | Gate between you and a reply | Branded RCS agent | iMessage via iBluSend | | Brand and agent registration | Required | None | | Carrier launch approval | Required, carrier by carrier | None | | 10DLC / A2P registration | Still applies to your SMS fallback | Not applicable | | Per-message carrier fee | Priced per message by your provider | $0 per message on your own line | | Native to GoHighLevel | Depends on the provider integration | Yes, real iMessage from a Mac bridge | None of that makes RCS bad. It makes RCS a channel with a gatekeeper, and iMessage a channel without one. If your outreach lives inside GHL and your prospects carry iPhones, one of those two starts producing replies the week you turn it on. What should your agency do about RCS this quarter? * Register anyway. It's two API calls now. Spending a day on something that used to take three weeks is obviously correct, and being unregistered when the queue clears would be silly. * Budget it as parity, not upside. Put RCS in the same mental column as having a website. You need one. It wins you nothing. * Do not promise a client an RCS launch date. You don't own stage two. Quote what you control. * Split your iPhone traffic out now. Pull your list, count how much of it is on Apple hardware, and route that segment to the channel that already delivers today rather than the one pending review. * Re-check in ninety days. If your agent has cleared carrier launch and reply rates justify it, scale. If it hasn't, you lost a day, not a quarter. By the time your agent clears carrier launch, so will everyone else's. The only question worth answering before then is what you'll have that they won't. Frequently asked questions. industry-news GoHighLevel iMessage marketing SMS compliance Zach Brick. Founder & CEO Zach Brick is the founder and CEO of iBluSend, the leading iMessage bridge platform for GoHighLevel and CRM automation. With deep expertise in messaging technology and marketing automation, Zach helps agencies and businesses achieve 98% open rates through iMessage marketing. Serial entrepreneur with 10+ years in marketing technology iMessage Marketing GoHighLevel Integration CRM Automation Marketing Technology Agency Growth