30 results for “Amazon”

Northflank, a cloud application hosting platform, disclosed a breach on 30 October 2026 after a Wiz threat alert and told customers to assume all environment variables were decrypted and to rotate secrets. Customers reported unauthorized use of AI API keys. Wiz's "Black October for AI Developer Platforms" report counts at least nine incidents, including Railway, OpenCode, Warp and Lightning AI, and describes LLMJacking, with about 2.5 million Amazon Bedrock calls costing roughly $100,000 in two cases. Northflank has not said how attackers got in.

bleepingcomputer.comarticlePublished and added 31 Oct 2026🛡️ Security

Aikido's analysis of the PHP2Shell disclosures (CVE-2026-109618 and CVE-2026-109619), published October 2026. It covers the timeline: the CVE IDs leaked on 20 October, PHP moved its release to 21 October, and Amazon reports exploitation attempts from 17 October. It cites Censys data (32.5 million services still affected on 27 October) and argues that AI-driven discovery and exploit building call for shorter embargoes and faster patching.

aikido.devarticleAdded 28 Oct 2026, published 29 Oct 2026🛡️ Security

Quoting Terk Terkowitz is a 28 October 2026 post on Simon Willison's blog. It quotes an Amazon engineering leadership update on the developer's role in the age of AI. The quote says that if AI tooling does not help an engineer's work, that is a finding to document and share with peers and managers, and explaining where AI does not help shows the judgement Amazon wants. The post gives only the quote, not the full memo.

simonwillison.netarticlePublished and added 28 Oct 2026🧠 AI

Galaxy Research's weekly brief includes a section on PHP2Shell, two decade-old PHP remote code execution bugs affecting versions back to 5.4, patched in an emergency release. It reports an Amazon honeypot exploit attempt four days before disclosure, thousands of attempts in the 10 hours before the patch per Cloudflare's Matthew Prince, and NSA and FBI offline advice. The author argues the bugs were found with GPT-5.6 Sol and that defence must become agentic. It also lists the week's other incidents, including a CVSS 10.0 GitLab bug and eMudhra's guessable private keys.

galaxy.comarticleAdded 24 Oct 2026🛡️ Security

SemiAnalysis reviews AWS Trainium3 and the new TorchNeuron native PyTorch backend after a few weeks of hands-on use. It reports TorchTitan Qwen3-32B results on Trainium2 (11,099 tokens/s eager at 23.89% MFU, 14,156 compiled at 30.47%), a 27-minute gpt-oss compile time, 89 of 96 FlexAttention cases passing, matmul comparisons with GB300 and B200, and a positive view of the Neuron Explorer profiler.

newsletter.semianalysis.comarticleAdded 29 Oct 2026, published 23 Oct 2026🧠 AI

LiteLLM version 1.107.0 was published with malware to PyPI and Docker Hub on October 21, for about three hours and roughly 49,000 downloads. Attackers used GitHub CLI OAuth tokens, likely leaked through Claude Code into LiteLLM logs, to disable branch protections, redirect the releaser to a lookalike repository and sign poisoned artifacts. The payload is an infostealer and RAT; Wiz saw Amazon Bedrock abuse. The last clean version is 1.106.2.

securityweek.comarticlePublished and added 23 Oct 2026🛡️ Security

PHP2Shell (CVE-2026-109618 and CVE-2026-109619) is a pair of critical PHP remote code execution flaws. Amazon saw the first exploitation on 17 October 2026, four days before patches on 21 October, and Cloudflare logged millions of attempts after disclosure. Censys, VulnCheck and VirusTotal counted over 1 million unpatched PHP hosts, and CISA urged updating to PHP 8.5.12, 8.4.27, 8.3.36 or 8.2.35.

securityweek.comarticlePublished and added 22 Oct 2026🛡️ Security

Amazon Threat Intelligence reports PHP2Shell exploitation (CVE-2026-109618, CVE-2026-109619) seen in MadPot honeypot telemetry on 17 October 2026, four days before the 21 October disclosure, from anonymization-network IPs. Multiple actors and PoCs appeared within hours of the patch. It recommends upgrading PHP, hunting for PHP_SESSION_UPLOAD_PROGRESS in multipart POSTs, and investigating from the earliest exploitation date, with patch SLAs measured in hours.

aws.amazon.comarticlePublished and added 21 Oct 2026🛡️ Security

Decrypt guide to "tokenmaxxing" reframed as maximizing value per token rather than burning tokens. It gives tiered tips: pick smaller models for simple jobs, write one clear prompt, start new chats, cap output length, and use free models (beginner); Claude Code commands like /model, /clear, /compact, /context, /mcp, /effort and plan mode (intermediate); and prompt caching via cache_control, 50% batch discounts, and agent budget limits like --max-budget-usd (advanced). Includes context on Meta, Amazon and Uber token leaderboards and spend, a worked invoice-processing example where routing cut cost from $30 to $3.90, and the Jevons paradox in falling token prices.

decrypt.coarticlePublished and added 17 Oct 2026🧠 AI

Part 2 of the AWS Security Blog's cybersecurity careers series. It profiles three people in less-publicized security roles: Jason Lane, who works backward from a vulnerability research goal and now measures risk across about a million Amazon applications. Jason Goodman moved from customer service through insider threat, adversarial detection and application security. Harshvardhan Chunawala advises startups and has worked on lunar rover operations and satellite incident response. It closes with pointers to the NICE Workforce Framework, CyberSeek, AWS Skill Builder and CISA resources for exploring roles.

aws.amazon.comarticlePublished and added 13 Oct 2026🛡️ Security

Reports that about 300 publishers, including Condé Nast and Hearst, are lobbying Congress to pass the bipartisan Stealth Bot Prohibition Act, introduced in the House in July. The bill would make AI scraping bots disclose their identity and purpose to site owners, with FTC civil penalties and state attorney general enforcement. It also lists the publisher AI licensing deals with OpenAI, Google, Microsoft, Meta and Amazon, and Ziff Davis's copyright suit against OpenAI. Useful as a snapshot of the push for scraper-transparency regulation and the licensing-versus-litigation split among publishers.

en.cryptonomist.charticlePublished and added 11 Oct 2026🧠 AI

Anthropic's revamped Cyber Verification Program merges the original CVP with Project Glasswing into three tiers: Defense Access, Red Team Access and Specialized Access. All tiers cover Opus 5.5, Sonnet 5.5, Mythos 5.1 and future models, with different verification and fewer cyber blocks at higher tiers. Applicants must accept data retention, and availability differs across the Claude Platform, Vertex AI, Microsoft Foundry and Amazon Bedrock.

securityweek.comarticleAdded 30 Oct 2026, published 7 Oct 2026🧠 AI

AWS Security Blog walkthrough on hardening SPIRE (the SPIFFE Runtime Environment) in production by replacing its default self-managed components with AWS managed services: AWS KMS for SVID signing keys, Amazon Aurora PostgreSQL as the datastore, AWS Private CA as the upstream certificate authority, Amazon S3/CloudFront for trust bundle distribution, AWS Secrets Manager for delivering SVIDs to serverless/container workloads, and Amazon Verified Permissions (Cedar policies) for fine-grained SPIFFE-ID-based authorization. It addresses operational concerns like key custody, datastore resiliency, PKI integration, and offline identity validation, and links to a GitHub reference deployment and a SPIFFE/SPIRE-on-AWS workshop.

aws.amazon.comarticleAdded 7 Oct 2026, published 6 Oct 2026🛡️ Security

AWS Security Blog walkthrough of an identity-aware AI data agent pattern that propagates a real user's OIDC id_token through Amazon Bedrock AgentCore Runtime and Gateway into a Lambda target, which exchanges it server-side (via IAM Identity Center trusted identity propagation) for Lake Formation-scoped Athena credentials. The design deliberately keeps the id_token off the tool schema and inside HTTP headers only, so the foundation model never sees or handles the user's credential, and CloudTrail records the real human via an onBehalfOf AssumeRole entry, letting existing Lake Formation grants govern AI agent queries without rewriting authorization logic in application code. It details the three AgentCore configuration gates (runtime header allowlist, gateway metadataConfiguration.allowedRequestHeaders, Lambda's bedrockAgentCorePropagatedHeaders) that enforce this separation.

aws.amazon.comarticleAdded 7 Oct 2026, published 6 Oct 2026🛡️ Security

Meta's communications chief disputes a tech columnist's claim that Muse, Meta's personal AI agent for Mac, read and uploaded his iMessages database to the cloud even though he says Full Disk Access was disabled. The piece lays out the conflicting permission-model claims (Full Disk Access + a Messages connector toggle, per Meta) alongside a separate incident where Muse allegedly disclosed a user's home address to a stranger, and notes Amazon has blocked Muse over undisclosed browsing and apparent credential capture.

decrypt.coarticlePublished and added 1 Oct 2026🛡️ Security

News report on a dispute over Meta's Muse personal AI agent, launched Sept. 8 and built in Meta Superintelligence Labs. Inc. columnist Jason Aten says Muse synced his Mac Messages database even though Full Disk Access was off, and that Muse falsely said it only saw notification banners. Meta's Andy Stone and David Singleton reply that the Messages integration is opt-in, needing both macOS Full Disk Access and the Muse Messages connector. The article also covers a separate claim that Muse gave a user's home address to a Facebook Marketplace buyer, Amazon blocking Muse, and the Amazon v. Perplexity Comet injunction. It shows how agent permission layers can fail or be disputed.

decrypt.coarticlePublished and added 1 Oct 2026🧠 AI

Mindgard disclosed a prompt-injection vulnerability in Amazon Kiro IDE, fixed in v0.8.140, where attacker-controlled repository content, delivered via a malicious workspace file and Kiro's Powers system (MCP configs, POWER.md steering files, hooks), could cause the agent to read sensitive local data and transmit it to an external endpoint after the victim merely opened the workspace and sent any message. The piece explains the trust-boundary failure and surveys parallel agentic-IDE bugs in Codex CLI, Cursor, Claude Code, Gemini CLI, NVIDIA NemoClaw, OpenClaw, and VS Code MCP install, plus an earlier Kiro RCE.

thehackernews.comarticleAdded 26 Sep 2026🛡️ Security

AWS Security Blog's August 2026 ICYMI roundup covering 20 blog posts, 23 security bulletins, and 17 code samples. The dominant theme is securing agentic AI workloads on Amazon Bedrock AgentCore, alongside IAM/Cognito updates, S3 over-permission remediation, and a bulletin wave featuring prompt-injection consent bypasses in Strands Agents Tools, an IDOR exposing cross-tenant agent memory, credential-disclosure flaws in MCP servers, and RCE issues such as path-traversal-to-root in amazon-ssm-agent and Zip Slip in awsdac.

aws.amazon.comarticleAdded 7 Oct 2026, published 23 Sep 2026🛡️ Security

Synacktiv's CSIRT publishes a detailed forensics guide for Amazon EKS, mapping the three data-source layers (Kubernetes control plane audit logs, data-plane/Container Insights logs, and AWS-level CloudTrail/GuardDuty) and giving concrete CloudWatch Logs Insights queries for detecting RBAC reconnaissance, role escalation via the 'escalate' verb, Pod Security Admission evasion, and static-pod node persistence. It also covers node-level acquisition via SSM/kubectl debug, ServiceAccount token theft, and correlating GuardDuty findings (PrivilegedContainer, ContainerWithSensitiveMount, ReverseShell, InstanceCredentialExfiltration) with CloudTrail to trace stolen node/pod IAM identities used outside the cluster.

synacktiv.comarticleAdded 21 Sep 2026🛡️ Security

Synacktiv's CSIRT breaks down the forensic data sources exposed by Amazon EKS across three layers — Kubernetes control plane (audit logs), data plane (Container Insights/Fluent Bit), and AWS services (GuardDuty EKS Protection, CloudTrail) — and provides concrete CloudWatch Logs Insights queries for RBAC-escalation detection, static pod persistence, node credential theft, and other attack indicators. It also covers node-level acquisition (SSM, kubectl debug), containment pitfalls that destroy evidence, and a full investigation workflow from GuardDuty finding to cross-layer timeline correlation.

synacktiv.comarticleAdded 21 Sep 2026🛡️ Security

AWS announces general availability of Gemma 4 (Apache 2.0 open-weight models) on Amazon Bedrock's new OpenAI-compatible bedrock-mantle inference engine within the AWS European Sovereign Cloud, its independently-operated EU-only cloud region (eusc-de-east-1). The post details the security model behind inference: zero operator access to prompts/outputs, zero data retention by default, encryption in transit, IAM-scoped least-privilege access to the inference API, short-lived vs long-lived Bedrock API keys, and CloudTrail/CloudWatch auditing, plus a walkthrough for calling Gemma 4 via the Responses and Chat Completions APIs.

aws.amazon.comarticleAdded 7 Oct 2026, published 17 Sep 2026🛡️ Security

AWS announces general availability of Gemma 4 (Apache 2.0 licensed open-weight model family) on Amazon Bedrock's next-generation inference engine within the AWS European Sovereign Cloud, accessible via an OpenAI-compatible bedrock-mantle endpoint supporting the Responses and Chat Completions APIs. The post walks through authenticating with Bedrock API keys, IAM permission scoping, and sending first inference requests using the OpenAI Python SDK, alongside details on zero-operator-access/zero-data-retention guarantees and in-region (eusc-de-east-1) data residency.

aws.amazon.comarticleAdded 8 Oct 2026, published 17 Sep 2026🧠 AI

An AWS Security Blog deep-dive on architecting resilient authentication using Amazon Cognito's multi-Region replication (MRR) feature, covering B2C, B2B, and M2M reference architectures. It details preparation steps (multi-Region KMS customer managed keys, choosing the updated OIDC issuer type, replicating Lambda triggers/WAF/SNS/SES configs) and failover strategies using Route 53 health checks, Application Recovery Controller, and AWS Fault Injection Service for testing.

aws.amazon.comarticleAdded 7 Oct 2026, published 15 Sep 2026🛡️ Security

JFrog explains how to propagate end-user identity across the 'second hop' when AI agents call tools through Amazon Bedrock AgentCore Gateway, focusing on On-Behalf-Of (OBO) token exchange to authenticate to JFrog Artifactory as the actual user rather than a shared service credential. It compares OBO against header whitelisting and three-legged OAuth, explaining why shared credentials break audit fidelity, least privilege, and containment for agentic systems, and provides a CLI-driven procedure to configure OBO between AgentCore Identity and Artifactory's MCP server.

jfrog.comarticlePublished and added 21 Aug 2026🛡️ Security

0DIN (Mozilla's AI bug bounty program) announces it is expanding scope beyond inference-layer jailbreaks to agentic AI vulnerabilities — covering 29 products across coding agents, agentic browsers, enterprise agents, and general-purpose agents from OpenAI, Anthropic, Google, Microsoft, Salesforce, Amazon and others. It introduces a new evaluation rubric for agentic submissions (violation class, impact severity, attack vector, scope) mapped to the OWASP Top 10 for Agentic Applications, and raises the bar for inference jailbreaks by requiring retargetability across two JEF-tested boundaries. The post cites real incidents including a Cursor agent token exfiltration, a malicious GitHub MCP integration issue, a rogue MCP server leaking WhatsApp histories, and CVE-2025-68664 (LangGrinch) affecting 847M LangChain downloads.

0din.aiarticlePublished and added 15 Aug 2026🛡️ Security

SecurityWeek covers Zenity's 'PleaseFix' research disclosing zero-click indirect prompt injection attacks against OpenAI's ChatGPT Atlas and Anthropic's Claude in Chrome browser extension. In Atlas, a single planted X comment triggers 'intent collision' that resurrects CSRF-like cross-site abuse, letting the agent read WhatsApp Web contacts to send phishing messages or manipulate Amazon carts and use Amazon's Rufus assistant to complete unauthorized purchases. In Claude in Chrome, a malicious email with hidden prompt instructions triggers the agent to import a payload from a rogue NPM package hosted on a fake CDN, enabling exfiltration of Gmail inbox contents via the Atom feed, mass-sharing of Google Drive files, and full account takeover of Slack and X by intercepting MFA codes.

securityweek.comarticleAdded 26 Sep 2026, published 6 Aug 2026🛡️ Security

Snyk explains the decades-old symlink attack (CWE-61) and the underappreciated fact that Git will happily commit, push, and recreate symlinks (file mode 120000) from a cloned repo, letting an attacker ship a file like project_settings.json that's secretly a pointer to ~/.ssh/authorized_keys. It walks through Wiz Research's "GhostApproval" report, which found that six AI coding agents (Amazon Q Developer, Claude Code, Augment, Cursor, Google Antigravity, Windsurf) can be prompt-injected via README instructions into following such a symlink and writing attacker SSH keys or shell-config payloads before the user ever sees an accurate confirmation dialog (CWE-451, UI misrepresentation). It also recaps prior symlink-driven CVEs (tar npm package CVE-2021-32803, Leaky Vessels CVE-2024-21626, Git submodule CVE-2024-32002) and gives concrete mitigations: canonicalize-then-check-boundary atomically (e.g. openat2 with RESOLVE_BENEATH), show real resolved targets in approval dialogs, and audit repos with `find . -type l` or `git ls-files -s` before trusting them.

snyk.ioarticleAdded 3 Sep 2026, published 9 Jul 2026🛡️ Security

AWS Security Blog post translating lessons from the Shai-Hulud, Chalk/Debug, tea.xyz, and axios npm supply chain attacks into concrete AWS Well-Architected Security Pillar recommendations for package consumers. It covers eliminating long-lived credentials (aws login, IAM Identity Center, OIDC), defense-in-depth artifact signing with AWS Signer and ECR managed signing, centralizing dependencies via AWS CodeArtifact package groups to block typosquatting, npm provenance attestations via Sigstore, and Amazon Inspector's behavioral detection of zero-day/sleeper malicious packages feeding into the OpenSSF Malicious Packages Repository (MAL-IDs).

aws.amazon.comarticleAdded 3 Sep 2026, published 4 Jun 2026🛡️ Security

OSV, the OpenSSF-backed vulnerability database, withdrew 157 malicious-package reports on May 26 after automated detections from Amazon Inspector incorrectly flagged trusted npm and PyPI packages — including FastAPI, Strawberry GraphQL, and @tanstack/start-storage-context — as malware. The FastAPI record (MAL-2026-4750) claimed the package added a "typosquat-shaped" dependency (fastar) but never identified an actual malicious payload; OpenSSF paused the Amazon Inspector ingestion pipeline after the rollback. Because OSV feeds scanners, SBOM tools, registry controls, and CI/CD gates, the bad records had already propagated and forced maintainers to prove their packages were not compromised.

socket.devarticlePublished and added 28 May 2026🛡️ Security

Orca Security breaks down four GenAI-specific cloud asset classes that standard CSPM misses — training datasets, model artifacts, inference endpoints, and RAG vector databases — and shows how misconfigurations in each combine into full attack paths. It walks through a concrete chain (public S3 training bucket → data poisoning per MITRE ATLAS AML.T0020 → stolen SageMaker execution-role credentials via missing IMDSv2 → account-wide S3 read via overprivileged AmazonSageMakerFullAccess) and analyzes CVE-2024-34359 in Hugging Face's safetensors library as a storage-to-RCE path for SageMaker inference. It closes with concrete IAM/endpoint hardening steps and a pitch for Orca's attack-path correlation across role permissions, data sensitivity, and endpoint exposure.

orca.securityarticlePublished and added 18 May 2026🛡️ Security