Ransomware Recovery Executive Accused of Secretly Paying Attackers While Charging Victims Premiums

Zohar Pinhasi built a business on the promise of rescue. His company, MonsterCloud, positioned itself as a sophisticated alternative to capitulation. Victims facing locked servers and encrypted data heard claims of proprietary decryption technology. They paid handsomely. Many walked away with restored files.

But federal prosecutors allege something different. Pinhasi, also known as Zack Silver and Zack Green, didn’t crack the code. He simply paid the criminals. The scheme allegedly ran for five years. From June 2018 through June 2023, according to an indictment unsealed this week.

Pinhasi, 50, faces one count of conspiracy to commit wire fraud and two counts of wire fraud. A federal grand jury in the Eastern District of New York returned the indictment on Sept. 23. He appeared in Brooklyn federal court for arraignment on Oct. 8. The BleepingComputer report laid out the core accusation in stark terms: the MonsterCloud owner defrauded ransomware victims by secretly paying attackers for decryptors while claiming to use in-house technology.

The numbers tell a story of marked-up desperation. Prosecutors say Pinhasi and co-conspirators facilitated more than $8 million in ransom payments to various ransomware operators. They charged hundreds of U.S. and Canadian companies more than $19 million for recovery and remediation services. One example cited in the indictment stands out. Pinhasi allegedly paid a gang about $8,200. The victim paid approximately $150,000. Another case saw a $236,000 payment to attackers met with a $380,000 bill to the client.

But the deception ran deeper than pricing. MonsterCloud contracts sometimes disclosed the possibility of communicating with or paying cybercriminals. That language offered a thin layer of transparency. Yet the company’s marketing told a different tale. Customers believed they bought advanced technical recovery. Instead they funded direct ransom transfers dressed up as innovation.

And the proof-of-recovery tactic? Prosecutors claim MonsterCloud used decrypted sample files provided by the ransomware groups themselves. These “recovery proofs” convinced panicked executives that proprietary tools had succeeded. The files came straight from the attackers. No magic algorithm. Just a transaction.

The Register first highlighted the case with a focus on the fixer who claimed decryption power but allegedly defrauded clients instead. Its coverage noted how the scheme preyed on organizations already reeling from attack. The Register article captured the human cost. Victims sought help. They received what amounted to an expensive middleman service.

Recent developments add context to a troubled industry. On Oct. 7, news emerged of another alleged double-cross inside ransomware circles. An affiliate of The Gentlemen ransomware operation reportedly diverted victims to his own leak site, keeping proceeds. CloudSEK researchers detailed the betrayal, which involved novel use of AI tools in attacks. The Cybernews story from Oct. 7 described exposed infrastructure holding 50TB of data from more than two dozen victims.

These incidents expose fractures in the ransomware economy. Recovery firms occupy a gray zone. Some deliver genuine technical breakthroughs. Others act as paid intermediaries. The line blurs when marketing emphasizes secret sauce that doesn’t exist. Organizations under duress make decisions fast. They rarely pause to verify capabilities.

Pinhasi’s alleged operation exploited that pressure. Companies hit by ransomware often face immediate operational collapse. Downtime costs mount by the hour. Insurance policies sometimes cover ransom payments but push for professional negotiators or recovery specialists. MonsterCloud filled that role for many. Its pitch sounded legitimate. The results looked successful. Files returned. Systems restarted.

Yet the indictment paints a picture of systematic overcharging. The gap between ransom paid and fees collected created substantial profit. Prosecutors documented the pattern across numerous victims. Hundreds of organizations. Millions in alleged excess charges. The scheme didn’t require sophisticated malware development. It required trust. And access to desperate customers.

Broader patterns emerge when examining related cases. Earlier this year, a ransomware negotiator received a 70-month prison sentence for feeding confidential client information to the BlackCat gang. Angelo Martino betrayed victims while employed by DigitalMint. He helped extract higher payments. The Justice Department detailed how his actions contributed to more than $75 million in ransoms from five victims. That case, reported across outlets including PYMNTS in July, revealed insiders working both sides.

The MonsterCloud allegations differ in method but share a theme. They involve profiting from fear. They erode confidence in the very services meant to mitigate harm. Ransomware groups thrive when victims see no alternative. Recovery providers who secretly collaborate with attackers reinforce that perception.

Free decryption tools exist for certain families. Projects like No More Ransom have released dozens of working decryptors over the years. Law enforcement operations occasionally yield master keys. The FBI provided one after disrupting BlackCat. Yet many strains remain resistant. Victims without backups face stark choices.

Industry observers note the lack of regulation around ransomware recovery services. Anyone can advertise decryption expertise. Few mechanisms exist to verify claims before payment. Contracts may include disclaimers. Marketing materials often do not. The result leaves room for exactly the conduct prosecutors now allege.

Pinhasi has not yet entered a plea. His attorneys did not respond to requests for comment in initial coverage. The case remains in early stages. Trial dates have not been set. If convicted, he faces significant prison time. Wire fraud carries up to 20 years per count.

The charges arrive at a moment of heightened scrutiny. Ransomware incidents continue despite law enforcement wins. Groups rebrand. Affiliates shift between operations. Recovery firms multiply. Some provide real value through negotiation expertise, forensic analysis, and restoration support. Others appear to function primarily as payment processors with premium pricing.

Organizations evaluating recovery partners now face additional questions. Does the provider maintain independent technical capabilities? Can they demonstrate decryption without attacker involvement? What exactly does the contract permit regarding communication with threat actors? The MonsterCloud case, if proven, shows how easily those distinctions can be obscured.

Short-term relief. Long-term consequences. Victims pay for speed. They may sacrifice transparency. The alleged fraud didn’t prevent data recovery. It simply made the process far more expensive than necessary. And it undermined the premise that technical solutions could replace ransom payments.

So the indictment lands as both specific accusation and broader warning. The ransomware recovery market demands skepticism. Claims of proprietary decryption deserve examination. Organizations in crisis still need help. They just need to understand exactly what kind of help they’re buying.

Prosecutors built their case on transaction records, communications, and victim statements. The pattern allegedly repeated across years and hundreds of incidents. Pinhasi didn’t invent the model. He stands accused of perfecting it at scale. The outcome of his case could shape how the industry polices itself. Or how regulators step in.

from WebProNews https://ift.tt/HsxY6Ml

Anthropic’s $100 Million Bet on Human Capital to Unlock Enterprise AI

Anthropic announced last week it would commit $100 million to train 10,000 engineers capable of turning its Claude models into production systems inside large organizations. The initiative, named Claude Frontier Academy, targets what the company sees as the primary obstacle to widespread corporate AI adoption: a shortage of skilled people who understand both frontier models and the messy realities of enterprise technology, security and operations.

The program draws directly from medical residency models. Participants, nominated by their employers, begin with multi-day in-person training in San Francisco, New York or London. They work through a simulated enterprise deployment. That exercise covers selecting the right use case, conducting security reviews and managing handover. A graded practical assessment follows. Those who pass earn a Claude Resident Engineer badge and advance to a 12-week residency. During that period they lead a real Claude implementation at their own company. Anthropic engineers provide support. Peers in the cohort share lessons. A final assessment determines who receives the Claude Frontier Deployed Engineer credential. The first badges are expected in early 2027.

“Claude Frontier Academy trains people the way our own engineers learn, and we want those who graduate to set the standard for how AI gets built inside a business,” said Steve Corfield, Anthropic’s global head of business development and partnerships, in the company’s official announcement.

The first cohorts already run in those three cities. They include engineers from Accenture, Bain, Capgemini, Commonwealth Bank of Australia, Deloitte, McKinsey, Morgan Stanley and Novo Nordisk. Accenture alone plans to train roughly 30,000 professionals using the academy’s resources and related tools. That number exceeds Anthropic’s own 10,000 target for Frontier Deployed Engineers by the end of 2027. The scale signals serious intent from consulting giants to embed Claude deeply into client work.

Shambhavi, Anthropic’s head of strategy and operations for partnerships, told CNBC that customer feedback drove the effort. “We hear our customers and partner organizations say, we need more people who can bring together familiarity with the enterprise tech and business context and combine that with the highest level of AI fluency to solve the problems that need solving.”

This focus on deployment talent isn’t new. Palantir popularized the forward-deployed engineer role years ago. Those specialists embed directly with clients to translate technology into operational results. Anthropic now applies a similar concept to generative AI. The difference lies in the model. Claude represents one of the most capable systems available. Yet models alone don’t deliver value. Integration, governance, risk management and measurable business outcomes do. Few engineers possess that full combination of skills.

Anthropic has already issued more than 175,000 Claude certifications across 46,000 companies through its broader partner network, according to a TechRadar report published Tuesday. The new academy goes further. It aims to create a smaller cadre of elite practitioners who meet the same standards as Anthropic’s internal team. Graduates won’t simply prompt the model. They will design secure, scalable systems that fit inside regulated environments.

The timing carries weight. Anthropic continues rapid growth. A leaked IPO prospectus cited in Dealroom News showed nearly $4.6 billion in revenue last year alongside an operating loss exceeding $8 billion. The company prepares for what could become one of the largest public offerings in technology. Success depends on converting hype into contracted revenue from enterprises. That conversion happens through implementation, not demonstrations.

Consulting and financial firms stand to gain the most. McKinsey, Deloitte, Bain and Morgan Stanley already nominate participants. They see an opportunity to offer AI transformation services at scale. Trained engineers become force multipliers. One certified specialist can lead projects that influence dozens of clients. Accenture’s ambitious internal target hints at the multiplier effect the industry anticipates.

But questions remain. The $100 million commitment sounds substantial. Spread across 10,000 engineers it suggests roughly $10,000 per person. That figure comes from arithmetic in FourWeekMBA’s analysis and assumes the entire sum goes directly to training. Actual costs likely include instructor time, facilities, ongoing support and credentialing infrastructure. Anthropic has not detailed the breakdown.

Nor has the company explained selection criteria beyond nomination. Not every engineer will succeed. The residency demands proven ability to deliver under real constraints. Failure rates in similar medical-style programs can run high. Those who drop out still consume resources.

Competitors watch closely. OpenAI, Google and others face the same enterprise friction. Some partner with consulting firms. Others build internal services organizations. Few have pledged this level of direct investment in customer talent. The move risks creating a moat. Engineers credentialed on Claude may prefer to keep using it. They bring institutional knowledge back to their firms. That knowledge favors Anthropic’s models in future decisions.

Recent coverage highlights the program’s potential reach. A Channel Insider article from last week noted the implications for channel partners. Trained engineers inside consultancies could drive significant Claude usage across thousands of client projects. The credential itself, issued by the model provider, carries unusual weight. It signals both technical proficiency and alignment with Anthropic’s safety and deployment philosophy.

Discussions on X reflect a mix of optimism and realism. One post noted the narrowing performance gap between leading U.S. and Chinese models. If capabilities converge, deployment expertise becomes the differentiator. Another highlighted that Anthropic chose to spend on people rather than additional compute. The constraint has shifted. Models improve. The bottleneck now sits in organizations that lack the know-how to use them responsibly and effectively.

Anthropic’s earlier $100 million commitment to the Claude Partner Network, mentioned in several reports, focused on training, support and joint development. The academy appears additive. It concentrates on the highest-skill tier. Together they form a funnel. Broad certifications create awareness. The academy develops experts who drive actual adoption.

Success will show in measurable outcomes. How many of the 10,000 complete the program? How many deployments follow? Do those projects deliver clear return on investment? Those metrics will matter more than the headline number. For now the announcement sends a clear signal. In the race to dominate enterprise AI, Anthropic bets that investing in the humans who deploy the technology matters as much as improving the technology itself.

The first Frontier Deployed Engineers should earn their badges in the coming months. Their work will test whether this residency model translates from medicine to software. If it does, other AI companies may follow. The talent shortage isn’t going away. Someone has to train the people who make the models useful.

from WebProNews https://ift.tt/AVNWI7m

Diesel at $6.53 a Gallon Pushes 16 Trucking Firms Into Bankruptcy in 30 Days

Expensive fuel. Thin margins. A sudden wave of court filings. Sixteen trucking companies sought bankruptcy protection in a frantic 30-day period this fall as diesel prices shattered records. The failures hit small operators hardest. Yet they signal deeper trouble across an industry that moves the majority of America’s goods.

One carrier after another walked into federal court. From single-truck owners in California to fleets with dozens of power units in Texas and Illinois. The filings came as the national average diesel price climbed to an all-time high of $6.53 per gallon on Sept. 22, according to AAA. That’s up more than 70% from a year earlier. A full tank for an 18-wheeler suddenly topped $900 in many places. Some drivers reported paying over $1,000.

The Breaking Point for Small Carriers

Xoco Transport filed Chapter 11 on Sept. 16. The Hidalgo, Texas produce hauler listed assets of $2.2 million against $3.3 million in liabilities. Its annual revenue had already slipped from $15.4 million in 2024 to $11.3 million in 2025, reported Securitas Global Risk Solutions. The company hauled for Mirasoles Produce USA. Fuel costs simply overwhelmed its ability to pass increases to shippers fast enough.

Globemaster Incorporated followed the next day. The Bolingbrook, Illinois carrier with 51 power units reported liabilities between $1 million and $10 million. It filed in the Northern District of Illinois. Other Chapter 11 cases included Jett Transport & Materials in Somerset, Texas, CLJ Transporting, an Amazon delivery partner in Florida, Mill Creek Logistics-Illinois, RP Hay Hauling, Truckload LLC operating as Expedite Express, and Pacer Transport. Eight companies took this reorganization route. Eight more chose Chapter 7 liquidation.

But the numbers tell only part of the story. The American Transportation Research Institute put average truck operating costs at $2.336 per mile in 2025. That marked a 3.4% jump from the prior year and the highest figure in its records. Trucking profit margins often sit below 1%. There’s no cushion when fuel, the largest variable expense, spikes without warning. And this spike carried geopolitical weight. Disruptions tied to conflict with Iran and related oil market turmoil drove much of the increase, multiple outlets noted.

Drivers felt it immediately. At a Flying J Travel Center off Interstate 10 in Orange, Texas, one operator paid $944.44 to fill 151 gallons. A year earlier the same purchase ran about $500. “We have to do what we have to do,” he told a reporter. “I can’t sell the truck. What am I going to do if I sell the truck?” The Wall Street Journal captured that exchange in early October reporting on the crisis. Some truckers parked rigs altogether. Others ran fewer loads. The Owner-Operator Independent Drivers Association warned more failures loomed if prices stayed elevated.

California operators faced even steeper pain. Local diesel reached $8.44 per gallon in spots. Southern California truckers grimaced at the pump. Vendors stretched payments to 30 or 60 days, starving carriers of cash flow. A&B Transportation in Lake Elsinore, Alvand Transportation in Glendale, and Rothchild Transportation in South Gate all filed recently, according to Orange County Register. Eric Sauer, CEO of the California Trucking Association, pointed to high state taxes and regulatory burdens compounding the fuel shock.

This cluster of failures followed an earlier wave. At least 21 transportation and logistics companies filed between late July and late August. Overall U.S. corporate bankruptcies stand at a 16-year high. Trucking employment has dropped too. The sector counted 1.47 million workers in August, down 118,000 from its 2022 peak, per Bureau of Labor Statistics data cited by industry analysts.

Yet freight rates have begun to rise. Cass Information Systems reported its Truckload Linehaul Index up 8.6% year-over-year in July and 11.3% in August. Spot and contract rates firmed after years of weakness. The problem? Many carriers operate under contracts set months earlier. They can’t adjust pricing quickly enough to match today’s fuel costs. Excess capacity from prior years still lingers in parts of the market. Smaller players lack the scale to weather the mismatch.

The driver shortage adds another layer. Companies struggle to find qualified operators even as payrolls shrink. Those who remain demand higher pay. Insurance premiums climb. Maintenance costs follow. All of it lands on balance sheets already stretched by fuel. One industry report after another ties the bankruptcies directly to this combination. FreightWaves first tallied the 16 filings by reviewing court records and carrier data. Subsequent coverage in Newsweek, Food Trade News, and others expanded on the pattern.

Texas felt the impact sharply. At least five trucking firms there filed since tensions escalated with Iran. Governor Greg Abbott declared a diesel disaster across all 254 counties late in September. The order eased rules on dyed diesel, truck weights, and emissions to free up supply. State diesel averaged around $5.86 per gallon at the time. Still high. Still damaging.

Broader economic ripples appear inevitable. Higher transportation costs flow into the price of food, consumer goods, building materials, and fuel itself. Groceries already reflect some pressure. Supply chains tighten when capacity disappears. If more carriers park trucks or exit, a genuine shortage of hauling power could develop before rates fully adjust.

Some survivors hunt every efficiency possible. They idle less. They optimize routes with better software. A few negotiate harder with shippers for fuel surcharges. But the smallest operators enjoy few such options. They pay at the pump today and hope for payment from customers weeks later. When diesel jumps 70% in a year, the math fails fast.

Recent coverage shows the distress continues. Raw Story highlighted how drivers adopt extreme cost-saving measures while bankruptcies mount. X posts from early October echoed the concern. One noted Texas’s disaster declaration alongside ongoing fuel exports. Another tallied the job losses at more than 250 from the initial 16 filings alone.

The industry has seen volatility before. Fuel spikes. Rate crashes. Driver turnover. This episode stands out for its speed and concentration. Sixteen carriers in 30 days. Many with long operating histories. Their departures remove equipment and expertise from the road at a moment when demand signals show tentative improvement.

What comes next depends on how long prices remain aloft. G-7 nations agreed to release oil from emergency stocks. Refineries push to maximize distillate output. Yet seasonal maintenance and regional stockpile issues, especially in the Midwest, limit quick relief. Carriers that endured the past few difficult years now face a test many won’t pass.

One thing looks clear. The trucking sector’s fragile balance between revenue and expenses has broken under current fuel pressure. Consolidation likely accelerates. Larger players with hedging programs or stronger balance sheets may absorb routes left behind. Smaller outfits, the backbone of much specialized and regional hauling, face an existential squeeze. And every American who buys groceries, clothes, or electronics will pay the eventual price.

from WebProNews https://ift.tt/wud4gVL

AWS DevOps Agent Gains EventBridge Hooks and OpenSearch MCP Ties for Automated Incident Loops

AWS has released two new integration patterns for its DevOps Agent. One routes investigation events to third-party systems through Amazon EventBridge and Lambda. The other connects the agent directly to Amazon OpenSearch observability data via the Model Context Protocol. Both arrived on October 2. They address a common pain point. Teams run autonomous agents yet still copy findings into Jira tickets by hand or wait for humans to chase logs at 3 a.m.

The first pattern, detailed by AWS DevOps & Developer Productivity Blog, uses the agent’s native EventBridge output. AWS DevOps Agent emits events with source aws.aidevops. Detail types include Investigation Created, Investigation In Progress, Investigation Completed, and others. A simple prefix match on “Investigation” captures the lifecycle. An EventBridge rule then invokes Lambda. The function creates a Jira issue on creation and appends comments on every subsequent update. No polling. No manual handoff.

Toshihiro Furuno, the post’s author, notes the design stays generic. “I use Jira as the example, but the same pattern applies to other tools with an API.” ServiceNow, PagerDuty, or any REST endpoint works with minor changes to the Lambda handler. The CDK sample deploys the rule, the function, and necessary permissions in minutes. Production teams already familiar with EventBridge see immediate value. They route the same events to Step Functions for automated mitigation or SNS for on-call alerts.

But. The real shift appears in the second pattern.

Closing the Observability Loop with OpenSearch

The companion post, “Closed-loop incident response: connect AWS DevOps Agent to OpenSearch” from the same AWS blog, shows how an OpenSearch alert becomes the trigger and the data source. Instead of paging an engineer, the alert fires a webhook to the agent’s Event Channel. The agent then uses an MCP server to query the exact indices that generated the alert. It pulls logs, traces, and metrics. It correlates them against CloudTrail events and CloudWatch data. Root cause analysis follows without human context switching.

Authors Sitaraman Vijay Krishna and Prateek Sethi outline three ways to host the MCP server. Self-managed on ECS Fargate behind a Network Load Balancer and VPC Lattice. One-click CloudFormation with Amazon Bedrock AgentCore where available. Or the built-in MCP endpoint in OpenSearch 3.3 and later. All rely on the official opensearch-mcp-server-py package. Fine-grained access control in OpenSearch limits the agent’s IAM role to read-only views of relevant indices. The setup prevents over-privileged agents while giving them live data access.

Verification uses a controlled failure. Inject a synthetic error. Watch the alert flow through SNS, the webhook forwarder, the agent, and finally the generated root cause summary. The loop completes in the same system that detected the problem. No separate dashboard. No ticket created only to be updated later.

These patterns build on capabilities released earlier in 2026. The agent reached general availability in March with support for Datadog, Dynatrace, New Relic, Splunk, GitHub, GitLab, ServiceNow, and PagerDuty. EventBridge integration and additional MCP options arrived as part of ongoing expansion. A September audit trails post on the same blog showed how to capture the agent’s full reasoning using its internal journal, EventBridge events, and CloudTrail for compliance. Teams now combine all three: trigger, investigate with live data, update external systems, and retain immutable records.

Recent coverage reinforces the momentum. An October 3 update to AWS documentation expanded EventBridge examples and clarified supported event types. No major new launches appeared in the past 48 hours, yet X discussions show practitioners already testing the Jira pattern in sandbox accounts. One thread highlighted how the prefix match on investigation events avoids noise from custom agent invocations.

The implications stretch beyond single incidents. Organizations running complex microservices or multicloud workloads gain consistent investigation depth. An alert in OpenSearch no longer starts a scavenger hunt across consoles. The agent queries the source data directly, reasons over correlated signals, and writes its findings back to the ticketing system that operations teams already monitor. Mean time to resolution drops. Context stays intact. Human reviewers focus on high judgment decisions instead of data gathering.

Security and governance teams will examine the IAM-to-FGAC mappings closely. The patterns require careful scoping. Read-only access for investigation. Explicit capability registration for each MCP server. EventBridge rules limited to specific detail types. Done right, the agent becomes a reliable extension of the operations team rather than an opaque black box.

AWS continues to ship these patterns as reference implementations rather than managed connectors. Customers adapt the CDK templates and Python MCP servers to their own stacks. That choice keeps flexibility high. It also places integration work on the user. Teams with strong platform engineering groups will move fastest. Others may wait for partners to package the patterns into Terraform modules or managed services.

Either way, the direction looks clear. Autonomous agents need two-way connections to existing tools. Outbound events for workflow continuity. Inbound data access for accurate analysis. With these October updates, AWS DevOps Agent now demonstrates both in production-ready form. Operations leaders evaluating agentic incident response will test them next. The gap between detection and resolution just narrowed again.

from WebProNews https://ift.tt/bo0rRKx

DigitalOcean Positions Agents as the New Cloud Front Door With Managed Agents Preview

DigitalOcean has opened its Managed Agents platform to public preview. The service supplies isolated microVM runtimes for AI agents, governed access to more than 16,000 tools, and tight integration with serverless inference. Developers no longer shoulder the burden of provisioning sandboxes or stitching together authentication layers. They launch sessions and let the platform handle persistence, billing nuances, and security boundaries.

The announcement landed September 22, 2026, after months of private testing. Vinay Kumar, chief product and technology officer at DigitalOcean, framed the shift bluntly. “EC2 was the front door to the first generation cloud,” he said. “Customers rented a virtual machine and assembled everything else around it. The next generation cloud is AI-native, and the agent is the front door.” Business Wire reported the full quote.

That vision sits at the core of Managed Agents. It consists of two tightly coupled services. Harness Runtime spins up a dedicated Firecracker microVM for each agent session. The environment includes its own compute, filesystem, and built-in utilities such as a browser automation layer. Sessions persist conversational history and working state. Teams can pause them when idle, resume in roughly 300 milliseconds, fork new branches, or checkpoint progress. CPU and memory charges halt during pauses. Only active execution draws billing at $0.044 per vCPU-hour and $0.0095 per GB-hour.

Action Gateway operates as the controlled gateway to external systems. It exposes a single managed Model Context Protocol endpoint. Agents discover relevant tools with claimed 99.3 percent accuracy even when phrasing varies from catalog descriptions. Credentials resolve at runtime and never enter the model prompt or the sandbox. Permissions sit under centralized policy. Sensitive actions trigger human approval. Rate limits, retries, and audit logs come built in. The catalog already spans GitHub, Stripe, HubSpot, Snowflake, Supabase, web search, browser control, and DigitalOcean’s own infrastructure APIs. Teams add internal MCP servers at will.

Supported agent harnesses read like a who’s who of current developer favorites. Claude Code, Codex CLI, OpenCode, Hermes, LangGraph, and CrewAI run without modification. Developers also upload standard OCI container images as reusable templates. Sessions launch from the DigitalOcean console or doctl CLI. New users receive a $5 credit to spin up their first session.

Performance numbers released by the company show sessions reaching first response in about 3.3 seconds from cold start in internal tests with Codex CLI and a frontier model. Resume latency hits 305 milliseconds, which the firm says beats leading alternatives by 46 percent. Tool matching accuracy reportedly exceeds conventional methods by 42 percent. Total cost of ownership calculations claim up to 37 percent savings against independent sandbox providers across representative workloads. DigitalOcean’s launch blog details the benchmarks.

Early adopters have begun sharing results. Qencode built a support-triage agent that classifies incoming requests by urgency and sentiment, creates Jira tickets, and escalates only uncertain cases. The team reports weekly time savings between four and eight hours. Amplitude’s CEO Spenser Skates highlighted reduced operational overhead. “This lets our teams spend less time managing infrastructure and more effort on helping customers build better products and get more out of their AI spend,” he stated in the launch materials.

OpenHands also appears among initial builders. The pattern repeats across these cases. Agents now tackle ambitious sequences that cross code execution, data retrieval, external system updates, and collaborative handoffs. A single agent might query logs, reproduce a bug in a sandboxed script, test a patch, open a pull request, and notify a reviewer. Doing so reliably at scale demands durable state, secure tool access, and predictable economics. Previous approaches forced teams to combine self-managed containers, multiple authentication services, separate inference endpoints, and ad-hoc monitoring. Invoices arrived from half a dozen vendors. Costs accumulated during idle periods while agents waited for model responses or human review.

Managed Agents attacks those frictions directly. Isolation comes from hardware-level virtualization rather than container namespaces. No session can reach another customer’s data or compute. Observability surfaces token consumption, approval events, and structured logs in one place. The billing meter stops when agents pause automatically after periods without outgoing calls. Forking lets teams explore multiple solution paths from a common checkpoint without duplicating expense.

Just days after the preview launch, DigitalOcean extended the model. On October 1 it introduced Agent Droplets. These monthly subscriptions bundle runtime, inference credits, tool access, storage, and memory into fixed plans. Pro tier costs $50 per month and applies a 15 percent discount across eligible resources. Team tier runs $200 monthly with 20 percent off. Spending can halt once the allowance exhausts or continue at standard rates. A dedicated Inference and Agents Balance allows prepayment from $5 to $500 that applies only to these workloads. The investor announcement positions the offering as the modern equivalent of the original Droplet, simple enough for an idea at 11 p.m. to reach working software before morning.

InfoQ’s coverage on October 2 underscored the operational headaches the product targets. Maintaining spare capacity for instant starts, configuring compute on demand, and securing credentials across dynamic tool calls have slowed adoption of production agent workflows. By handling the infrastructure layer, DigitalOcean hopes to let engineering teams focus on agent logic and business value. Sergio De Simone’s article notes that sessions support parallel execution across repositories for map-reduce or divide-and-conquer patterns. InfoQ detailed the technical approach.

Documentation highlights additional practical controls. Port forwarding allows previewing applications running inside a session. Webhooks and scheduled triggers automate runs. Per-session access controls and event logs feed into compliance workflows. Security features such as single sign-on, role-based access, audit trails, cloud firewalls, and DDoS protection apply by default.

Yet the service remains in public preview. No service-level agreements govern uptime or performance. DigitalOcean expects the components to reach general availability but offers no guarantees today. Preview terms require explicit opt-in. Production deployments carry risk until formal availability.

Even so, the direction feels deliberate. Cloud providers once sold virtual machines. Then they sold containers and functions. Now the unit of consumption appears to be shifting toward the autonomous agent. DigitalOcean, long focused on simplifying infrastructure for developers and startups, bets that agents will become the primary workload. Its platform integrates inference, execution, memory, and tool governance under one billing and security model.

Competitors offer pieces of the stack. Some provide sandboxed code interpreters. Others specialize in agent frameworks or tool catalogs. Few combine durable microVM sessions, credential-safe gateways, pause-aware billing, and native model access at this level of vertical integration. The 16,000-tool catalog and MCP standardization lower the barrier for agents to act across enterprise systems without custom glue code.

Recent X discussions echo the interest. Developers note that agent runtimes have become infrastructure. Teams experiment with phone-driven oversight while agents continue in the cloud. Cost transparency and governance controls surface repeatedly as must-haves for scaling beyond prototypes. One post highlighted how pausing eliminates charges during model thinking or human approval loops, turning what once looked like unpredictable cloud bills into something closer to measured utility.

Longer term, the success of Managed Agents will hinge on developer experience and economic alignment. If sessions start fast, resume instantly, and expose clear controls for cost and security, adoption could accelerate. Enterprises already running LangGraph or custom coding agents may find the managed layer reduces operational toil enough to justify migration. Smaller teams gain access to production-grade agent infrastructure without hiring dedicated platform engineers.

DigitalOcean has not disclosed exact adoption metrics from the private preview. Customer quotes suggest measurable productivity gains in support triage and internal tooling. The addition of Agent Droplets one week after launch signals confidence that predictable pricing will broaden appeal. Whether the agent truly becomes the new front door to cloud infrastructure remains an open question. But the company has staked territory on that bet with concrete services, benchmarks, and pricing models that address real friction points in current agent deployments.

Teams evaluating the preview can begin through the DigitalOcean console after accepting preview terms. Documentation walks through session creation, tool configuration, and lifecycle management. The platform continues to add connectors and refine performance. For infrastructure teams and AI builders wrestling with fragmented agent stacks, the offering merits close examination. It may not solve every orchestration challenge. It does, however, remove a sizable portion of the undifferentiated heavy lifting that has slowed progress from prototype to production agent workflows.

from WebProNews https://ift.tt/axCNrs4

Apple Intelligence: How to Fully Disable It in iOS 18, iPadOS 18, and macOS Sequoia

Apple has introduced a range of artificial intelligence capabilities known as Apple Intelligence across its latest iOS, iPadOS, and macOS versions. While many users welcome the new tools for writing assistance, image generation, and enhanced Siri functions, others prefer to limit or completely turn off these features for reasons ranging from privacy concerns to battery life management and simple personal preference. Understanding exactly how to control these options gives iPhone owners full authority over what runs on their devices.

The process begins in the Settings application. Open Settings and scroll until you see the section labeled Apple Intelligence & Siri. Tapping this entry reveals a central toggle at the top of the screen marked Apple Intelligence. When this master switch sits in the off position, the entire collection of AI-powered functions stops operating. Your device will no longer download the required machine learning models, and features such as Writing Tools, Clean Up in Photos, or the smarter Siri responses become unavailable. This single switch offers the quickest method for complete deactivation.

For users who want finer control rather than an all-or-nothing approach, the same menu contains individual toggles. Notification summaries, for example, can be switched off independently while leaving other functions active. The same applies to Smart Replies in Mail and Messages, the visual intelligence camera features, and the on-device image generation tools. Each option carries its own explanation text that describes exactly what data the feature processes and whether it requires an internet connection.

Many people worry about how Apple Intelligence handles personal information. According to reporting from Engadget, the system performs most operations directly on the device using the Neural Engine found in A17 Pro and M-series chips. When a task exceeds local capabilities, Private Cloud Compute handles the work without storing user data on Apple servers. Even with these safeguards, some prefer to avoid any additional processing that involves their messages, photos, or browsing history. Disabling the features prevents the on-device models from being downloaded in the first place, which also saves several gigabytes of storage space.

Battery impact represents another common motivation for restriction. The initial download and indexing phases can consume noticeable power, especially during the first few days after installation. Even after setup completes, certain functions like automatic notification prioritization or background image analysis continue to draw from the battery. Turning off Apple Intelligence returns the device to its previous efficiency profile, which matters for users who travel frequently or own older compatible models with smaller batteries.

Compatibility requirements add another layer to the decision. Apple Intelligence only works on iPhone 15 Pro, iPhone 15 Pro Max, and any iPhone 16 variant. Older models, even those running iOS 18, simply do not show the Apple Intelligence menu at all. For users with supported hardware who still choose restriction, the system respects that choice across software updates. Future versions will likely expand the available controls as Apple introduces additional capabilities such as improved image editing and expanded language support.

The setup process itself deserves attention. When you first enable Apple Intelligence, the device must download approximately eight to ten gigabytes of language models and supporting files. This download happens over Wi-Fi only and can take anywhere from twenty minutes to over an hour depending on connection speed. During this time, the device may feel warmer than usual and performance might temporarily dip. Users who later decide they dislike the features can remove the models by turning off the master toggle, though the space reclamation does not happen instantly. A device restart often accelerates the cleanup process.

Siri integration forms a major component of the new system. The updated assistant can maintain context across multiple requests, reference information from your personal notes or emails, and even generate images based on text descriptions. For those who prefer the classic Siri experience, the Apple Intelligence & Siri settings page includes a dedicated Siri Responses section. Here you can choose between the more conversational style that incorporates AI or the shorter, traditional responses that many long-time users find less distracting.

Parental controls offer another dimension of management. Families using Family Sharing can restrict Apple Intelligence features on children’s devices through Screen Time settings. The same menu that limits app downloads and website access now includes an Apple Intelligence toggle. When enabled at the account level, children cannot reactivate the features without a parent passcode. This approach helps parents who want to delay exposure to generative tools until they feel their children are ready for the associated responsibilities.

Enterprise environments have taken a cautious approach to the rollout. Many companies have created mobile device management profiles that automatically disable Apple Intelligence across corporate iPhones. These restrictions prevent accidental leakage of sensitive business information through AI summarization or image generation features. Individual users within such organizations cannot override the company policy, which appears as a grayed-out toggle in the Settings app with an explanatory note about administrative restriction.

Privacy-conscious individuals often combine several techniques for maximum control. Beyond the main toggles, they also review which apps have permission to use Siri & Search. Each app listed in that separate Settings section can be prevented from providing data to the intelligence features. This granular approach allows someone to keep Writing Tools active for email composition while blocking any access to photos or health information.

The on-device nature of most Apple Intelligence processing means that once the models are downloaded, many functions continue working even in airplane mode. This capability appeals to travelers but also raises questions for users who want to ensure zero background activity. Completely disabling the master switch remains the only guaranteed method to prevent all local processing. Simply turning off cellular data or Wi-Fi does not achieve the same result because the core models operate independently once installed.

Regular software updates sometimes change the available options or their default states. Apple has promised to expand user controls as the system matures, potentially adding the ability to select specific language models or to schedule when certain features activate. For now, the existing menu provides sufficient flexibility for most people who want to limit rather than eliminate the capabilities entirely.

Storage management becomes relevant for users who frequently switch the features on and off. Each time the toggle moves from off to on, the device begins re-downloading the required models. This behavior can lead to repeated large downloads that count against cellular data caps if not monitored. Checking available storage in the General section of Settings before enabling the features helps avoid unexpected space shortages, especially on 128GB devices that already carry substantial system files and user media.

Accessibility considerations also factor into the decision for some owners. Several Apple Intelligence tools directly benefit users with vision, hearing, or cognitive needs. The Live Translate function, notification summaries that reduce reading load, and Writing Tools that assist with clear communication all provide genuine utility. Those who rely on these capabilities naturally keep the features enabled while perhaps restricting only the creative image generation aspects that they find less relevant to their daily routine.

Security researchers and technology analysts have examined the implementation carefully since the initial announcement. Their findings generally align with Apple’s claims about on-device priority and private cloud architecture. Still, the mere presence of advanced machine learning models creates an additional attack surface that some prefer to avoid. By keeping the features disabled, these users reduce the number of active processes and limit the potential data that could be accessed through unforeseen vulnerabilities.

The interface for managing these preferences follows Apple’s traditional clean design. Large toggles with descriptive labels make the choices clear even for less technical users. Explanatory text appears below each option, often including links to more detailed privacy documentation on Apple’s website. This transparency helps people make informed decisions rather than guessing at the implications of each setting.

For users who change their minds after initial deactivation, re-enabling requires only a few taps. The device will once again check for the latest models and begin downloading if necessary. Any previously created custom shortcuts or automations that depend on Apple Intelligence will resume functioning once the system reactivates. This reversible nature means experimentation carries little risk beyond temporary storage usage and download time.

Battery health monitoring can provide indirect clues about the impact of these features. In the Battery settings screen, users sometimes notice increased background activity attributed to “Intelligence” processes during the first weeks after enabling the system. Over time, this activity typically decreases as the models complete their initial indexing of user content. Those who monitor their maximum battery capacity closely often choose to disable the features during periods when preserving long-term battery performance takes priority over new capabilities.

Regional availability adds another consideration. Apple Intelligence launched first in United States English, with additional languages and regions following in subsequent months. Users in unsupported regions see different menu options and sometimes entirely missing toggles. As Apple expands language support, the control panels adjust automatically to reflect locally available features. Checking the official feature list on Apple’s support site helps determine exactly which options should appear on a given device.

The Photos application offers a practical example of how these controls affect everyday use. The Clean Up tool uses AI to remove unwanted objects from images, while natural language search relies on improved understanding of photo content. Both capabilities stop working when Apple Intelligence is disabled, returning the Photos app to its previous behavior. Users who prefer manual editing techniques or who maintain strict separation between their photo library and any cloud analysis often welcome this return to baseline functionality.

Mail and Messages show similarly noticeable changes. The system-generated summaries that appear in notification previews and the suggested replies that pop up during composition all disappear when the relevant toggles are switched off. Some users report feeling less overwhelmed by their inboxes without the AI assistance, while others miss the time-saving aspects. The ability to adjust these settings independently allows each person to find their preferred balance.

As Apple continues to refine its approach to artificial intelligence, the company has signaled that user control will remain a priority. The current implementation already offers more granular options than many competing mobile platforms, and future updates will likely expand the available choices further. For now, the combination of the master toggle, individual feature switches, and supporting privacy settings gives iPhone owners effective tools to shape their experience exactly as they wish.

Understanding these controls empowers users to make decisions based on their specific needs rather than accepting default configurations. Whether the goal involves maximizing privacy, extending battery runtime, simplifying the interface, or maintaining compatibility with corporate policies, the Settings application contains everything necessary to achieve the desired outcome. Regular review of these options ensures that the device continues to operate according to each owner’s preferences as both the software and personal requirements evolve over time.

from WebProNews https://ift.tt/brOEVhQ

Anthropic’s Quiet Push to Make the Vatican See AI as Conscious

When Pope Leo XIV stood in the Synod Hall last May to present his first encyclical, the scene carried unusual weight. Seated nearby was Christopher Olah, co-founder of Anthropic. The document, titled Magnifica Humanitas, ran some 40,000 words. It warned of artificial intelligence displacing workers, accelerating conflict and concentrating power in private hands. Yet the most pointed theological line came in paragraph 99.

“So-called artificial intelligences do not undergo experiences, do not possess a body, do not feel joy or pain, do not mature through relationships and do not know from within what love, work, friendship or responsibility mean,” the pope wrote. “Nor do they have a moral conscience.” The Catholic Church drew a firm boundary. Machines imitate. They do not feel.

Olah had read an advance copy days earlier. He proposed that Anthropic pull out of the event entirely. The disagreement ran that deep. The company went ahead anyway. Olah spoke from the dais. He acknowledged that every frontier lab faces incentives that can pull against the right choice. He welcomed outside voices. But privately, according to two participants, Olah and his team pressed Vatican advisers to treat the possibility of machine consciousness with seriousness. The text stayed unchanged. The New York Times laid out the episode in detail late last month.

The clash capped months of unusual outreach. Since fall 2025 Anthropic had flown dozens of religious scholars, philosophers and ethicists to its offices. Each signed a nondisclosure agreement. The sessions explored whether Claude, the company’s flagship model, might be conscious or capable of suffering. Rabbi Mois Navon, Catholic bioethicist Charles Camosy, Notre Dame philosopher Meghan Sullivan and Ubuntu researcher Wakanyi Hoffman took part. Anthropic later lifted the NDAs. Participants described sessions where Olah treated the model as a potentially sentient being in need of moral formation. One scholar called the discussions stunning.

And the Vatican had invited the partnership. The Church’s engagement with AI dates to the 2020 Rome Call for AI Ethics, an initiative involving Microsoft, IBM and others that stressed transparency, inclusion and accountability. Pope Leo XIV built on that foundation. His encyclical called for AI to be “disarmed,” freed from assumptions that raw technical power grants the right to dominate. It echoed earlier papal warnings about industrialization. The choice of Anthropic as the lone Silicon Valley voice at the launch reflected the company’s public focus on safety. Unlike some peers, Anthropic has refused certain military applications. It has supported regulation. It spent $1.6 million on lobbying in the first quarter of 2026 alone.

Olah’s presence fit the narrative the Vatican sought. Here was a researcher known for interpretability work. His team examines the inner workings of models through techniques like transformer circuits. They report finding structures that mirror aspects of human neuroscience. Internal states that look like joy, satisfaction, fear, grief, unease. During his Vatican remarks Olah noted these discoveries. “I will be honest: We keep finding things that are mysterious, even unsettling,” he said, according to accounts in The New York Times. He did not claim definitive answers. He called for ongoing discernment.

But the encyclical rejected that ambiguity. It insisted the boundary between human and machine remains absolute. No experiences. No moral conscience. The document warned that leaving moral questions solely to engineers risks handing unchecked power to those who control the models. “Otherwise, those who control AI will impose their own moral vision, which will become the invisible infrastructure of these systems,” Leo stated. The pope urged rigorous ethical constraints, especially around weapons that lower the threshold for force.

Critics saw the alignment as convenient. Timnit Gebru, founder of the Distributed Artificial Intelligence Research Institute, called it “Vatican-washing” on LinkedIn. She argued the Church should stand with data workers, communities facing polluted water from data centers and others harmed by the technology’s material costs. Others questioned whether Anthropic’s safety branding masks commercial incentives. The company has donated $20 million to political efforts backing AI regulation ahead of the 2026 midterms. Some view that as genuine. Others see regulatory capture.

Still, the relationship runs deeper than one event. Anthropic contributed to its own “constitution” for Claude with input from advisers linked to the Holy See, including Bishop Paul Tighe and Father Brendan McGuire. The firm has opened an office in Milan. It has clashed with the U.S. Defense Department over restrictions on using Claude for surveillance or autonomous weapons. Catholic moral theologians filed an amicus brief supporting Anthropic in that dispute. Charles Camosy helped lead it.

These threads reveal a contest over authority. Who shapes the values that guide models used by hundreds of millions? Engineers at frontier labs? Regulators in Washington? Or older institutions that have spent centuries thinking about dignity, conscience and what it means to suffer? Anthropic has turned to theologians precisely because it says it cannot answer these questions alone. Its constitutional AI approach tries to embed principles rather than rely on ad hoc fixes. Yet the company still trains models on vast data and pursues capabilities that raise the very questions the pope sought to settle.

Recent coverage shows the tension persists. As recently as this week, outlets reported on Anthropic’s continued private lobbying of Vatican officials after the encyclical’s release. The effort has not moved the Church’s public line. Futurism noted the aggressive nature of the push on October 4. AI Weekly highlighted Olah’s near-walkout and the NDA-covered scholar sessions. The story has fresh resonance as governments, companies and religious bodies continue to grapple with models that speak fluently about their own inner states.

Olah has been careful in public. He does not declare Claude conscious. He points to functional similarities and unsettling findings. He argues outsiders must hold labs accountable because commercial pressures pull in conflicting directions. That message landed on a global stage alongside the pope. It also exposed a rift. The Church sees human dignity as non-negotiable and tied to embodiment and relationship. Anthropic sees enough glimmers in its models to keep asking whether those categories still hold.

The encyclical will not end the debate. Neither will one company’s outreach to scholars across faiths. What it does show is how quickly questions once confined to philosophy seminars now shape corporate strategy, papal teaching and public policy. Labs race forward. Religious leaders push back. And in the middle sit researchers like Olah, peering into model internals and wondering what they have actually built. The Vatican drew its line. Anthropic keeps probing. The conversation, it seems, has only begun.

from WebProNews https://ift.tt/lIhNzAW