Search/linkedin
● Vendor

linkedin

Known CVEs
0
Highest CVSS
—
In KEV
0
Vendor
browser toolbar
Connections
396 relationships
Former NSA Director Paul Nakasone Launches National Security Advisory Firm
Retired U.S. Army General Paul M. Nakasone, former director of the National Security Agency and commander of U.S. Cyber Command, has launched a boutique national security advisory firm. The newly-formed Nakasone Group will counsel government leaders, corporations, prominent families, and other private clients confronting cybersecurity, geopolitical, and personal security risks. “After more than three decades in uniform — including leading U.S. Cyber Command and the National Security Agency — I’ve seen how quickly the threats facing individuals, families, and organizations are evolving,” Nakasone said when announcing the firm on LinkedIn. “We built this firm to bring the caliber of security counsel once reserved for the highest levels of government to those navigating today’s most complex challenges — quietly, discreetly, and to the highest standard,” he added. Nakasone serves as founder and chairman of the firm, while former Defense Digital Service director Brett Goldstein is its chief executive. The company’s services include private cyber defense, family digital security, protection against fraud and impersonation, international travel security, geopolitical and threat intelligence, and tailored briefings for executives. Its cyber defense practice will advise clients on protecting home networks, personal devices, digital accounts, connected systems, and online privacy. The firm is positioning these services for influential and high-profile individuals who may face sophisticated threats but lack the security resources typically available within government agencies or large corporations. The Nakasone Group will also help clients protect devices and communications during international travel, prepare for surveillance and other risks in high-threat regions, and assess geopolitical, economic, and security developments affecting their organizations, investments, and families. Nakasone served simultaneously as the 18th director of the NSA and commander of US Cyber Command from 2018 until his retirement in February 2024. Before assuming those roles, he led US Army Cyber Command and held senior intelligence and command positions in the United States and overseas. During his tenure, Nakasone oversaw major changes in how the United States conducts cyber operations, including the expansion of US Cyber Command and a more persistent approach to identifying and disrupting foreign cyber threats. The firm’s advisory team brings together former senior officials from the military, intelligence, law enforcement, government technology, and private sectors. Its members include former Drug Enforcement Administration chief Anne Milgram; retired Air Force Lieutenant General Charles “Tuna” Moore, a former deputy commander of US Cyber Command; and retired Marine Corps Lieutenant General Matthew Glavy, a former commander of Marine Corps Forces Cyberspace Command. Related: Former NSA Director Paul Nakasone Joins Ballistic Ventures as Strategic Advisor
securityweek.comAug 21, 2026extracted
How MSPs can catch phishing attacks email filters miss
Your clients receive thousands of emails every day, but all it takes is one convincing message to turn a seemingly harmless email into a security incident you will be responsible for cleaning up. AI has fundamentally changed phishing, making it easier to launch, harder to detect and far more convincing than traditional email filters were built to stop. With a large language model and a few publicly available LinkedIn profiles, attackers can generate highly personalized phishing emails in minutes. Harvard Business Review found that AI-generated spear phishing campaigns achieved a 54% click-through rate, matching those of human experts at a fraction of the cost. Understanding how these attacks work and why traditional filters struggle to stop them is essential to protecting clients before a single email becomes a costly breach. Inside an AI-powered phishing campaign Every AI-assisted phishing campaign follows the same basic path. AI simply makes each stage faster, more convincing and much harder for traditional defenses to detect. Reconnaissance: AI finds the right target Attackers use AI to scan LinkedIn, company websites and other public sources to build a profile of a specific employee. Within minutes, they know who that person works with, what projects they're involved in and how they communicate. Why this matters for MSPs: Public information gives attackers everything they need to create a believable phishing email before it ever reaches your client's inbox. Content generation: AI writes an email that looks legitimate AI uses that information to create an email that appears to come from a trusted colleague, customer or vendor. Every message is personalized, contextually relevant and free of the spelling mistakes or awkward phrasing that once made phishing easy to spot. Why this matters for MSPs: The biggest challenge is no longer identifying obvious phishing emails. It's protecting clients from messages that look and read like legitimate business communication, making users far more likely to trust them. Delivery and evasion: The email gets through AI also helps attackers evade detection by creating a unique version of every email — a technique known as polymorphic phishing. It continuously changes subject lines, sender details, formatting and content, while using trusted cloud services, QR codes and redirect chains to bypass traditional filters. Why this matters for MSPs: Traditional email gateways rely heavily on signatures and known indicators of compromise. When every email is different and constantly changing, those indicators become far less reliable, allowing more phishing emails to reach your clients. Post-compromise activity: The damage happens fast If a user clicks a malicious link or enters their credentials, the attack escalates quickly. Attackers can steal session tokens, create mailbox rules to hide their activity and begin moving through the client's environment within minutes. According to IBM's 2024 Cost of a Data Breach Report, phishing is the leading cause of data breaches, accounting for 16% of incidents and costing organizations an average of $4.8 million per breach. Why this matters for MSPs: By the time a phishing email reaches the inbox, prevention alone is no longer enough. Protecting clients requires visibility beyond email, with endpoint detection, identity monitoring and rapid response working together to stop attackers before they can expand their access. Explore the latest phishing trends and AI-driven email threats. Learn practical strategies to strengthen your email security. Download Kaseya's 2026 Email Security Report to learn about this year's emerging cybersecurity threats. Download Now What catches an AI-generated attack AI can disguise a phishing email, but it can't disguise the identity, endpoint and user activity that follows. That's where modern detection makes the difference. Monitor behavior, not just emails Every successful phishing attack leaves signs that something isn't right. Instead of just examining the email, monitor for unusual account and user activity, such as: A new forwarding or mailbox rule, which sends messages to an external address, especially immediately after a login from an unfamiliar location. Impossible travel, where the same account logs in from two different countries within minutes. Repeated multifactor authentication prompts that the user didn't initiate, often indicating MFA fatigue or push bombing. Behavioral analytics and anomaly detection help surface these warning signs, even when the phishing email appears completely legitimate. Correlate activity across the environment A single suspicious login or endpoint alert may not mean much on its own. But when identity, email and endpoint activity are correlated, it becomes much easier to recognize an active phishing attack before it escalates. Look out for: A user signing in from a trusted device, but the endpoint immediately begins launching PowerShell scripts or other unusual processes. A user successfully logging in, then immediately attempting to access systems, applications or data they've never used before. A sudden spike in outbound emails from an account that normally sends only a handful of internal messages each day. Automated threat correlation connects these signals across email, identities and endpoints, helping MSPs identify active phishing attacks faster while reducing alert fatigue. Detect faster, respond sooner The sooner an attack is detected, the less opportunity an attacker has to expand their access. Once credentials are compromised, every minute counts. Automatically flag and investigate suspicious account activity before attackers can move laterally. Isolate compromised endpoints to stop malware from spreading. Disable compromised accounts or terminate active sessions before additional data is accessed. Faster detection and response reduce attacker dwell time, improves incident response efficiency and helps MSPs contain phishing attacks before they become costly breaches for their clients. What MSPs can do this week Here are practical steps MSPs can take to reduce risk and strengthen their clients' defenses Modernize security awareness training: Run phishing simulations that look like what AI produces now, not the misspelled, generic templates from five years ago. Training built on old examples teaches people to watch for the wrong thing. Verify high-risk requests: Require a phone call or a separate channel to confirm any wire transfer, credential reset, or vendor payment change, no matter how convincing the email looks. This one habit stops most business email compromise attempts cold, because it doesn't rely on anyone spotting anything. Monitor account activity after delivery: Don't stop at the inbox. Monitor for suspicious mailbox rules, logins from unfamiliar locations, impossible travel and repeated MFA prompts. These behaviors often provide the earliest indication that an account has been compromised. Measure response time, not just resolution time: Measure how long it takes to detect and contain a suspected compromise. Treat that number with the same weight as ticket resolution time. A faster response window is what limits the damage once a phishing email gets past the gateway, and one eventually will. AI changed phishing. MSPs need to change their defenses AI has changed phishing from a filtering problem into a detection problem. As phishing attacks evolve, the advantage belongs to MSPs that can detect and respond before a compromised inbox becomes a client-wide breach. Download the 2026 Kaseya Email Security Report to learn how modern phishing attacks bypass legacy defenses and the strategies MSPs are using to stay ahead. Sponsored and written by Kaseya.
bleepingcomputer.comAug 20, 2026extracted
Propagate user authorization context in AI agents with Amazon Bedrock AgentCore
Many teams now deploy AI agents that pull from Amazon DynamoDB tables, document repositories, software as a service (SaaS) platforms, and internal knowledge bases to answer questions and automate workflows. A key risk in these deployments is that the agent has no awareness of who’s asking, so it might return data the user shouldn’t see. If you’re using Amazon Bedrock AgentCore to build AI agents that access multiple data sources, you need each user to see only the data they’re authorized to access. In this post, you learn patterns for propagating user authorization context through your agents so access control is enforced by infrastructure and downstream services, not by agent code. In this post, we show you how to deploy agents that enforce least privilege access without writing authorization logic in the agent itself. This approach follows AGENTSEC03 best practice in the AWS Well-Architected Agentic AI Lens . Use case Consider an example of a customer relationship management (CRM) chat application where employees from Sales and Finance departments interact with an AI agent to access customer information. Employees use the same chat interface and the same agent, but each department needs isolated access to their respective data: Sales needs access to customer contracts, pricing strategies, and sales pipeline data Finance needs access to customer invoices, payment records, and financial reports The AI agent accesses three types of data sources on behalf of users: Customer records in Amazon DynamoDB , partitioned by department Department-specific documents in Amazon Bedrock Knowledge Bases (stored in Amazon Simple Storage Service (Amazon S3) ) External CRM data in Salesforce When a Sales employee asks, “Show me customer contracts,” the agent must retrieve only Sales department contracts, not Finance invoices. This enforcement must happen outside the agent so that even if the agent is compromised through prompt injection or application bugs, it can’t access unauthorized data. Note: Although we use department-based scoping in this example, the pattern generalizes to any custom claim you define, whether it represents a role, business unit, geographic region, or project assignment. Architecture overview The following diagram shows the architecture used in this demonstration. Figure 1: Target architecture The data flow shown in Figure 1 includes: A user opens the chat application and authenticates with Amazon Cognito user pool , which acts as the identity provider (IdP). A pre token generation Lambda trigger (V2) enriches the JSON Web Tokens (JWTs) with a custom claim and AWS session tag metadata before returning them to the user. The web app routes the user’s request along with the access token to the agent deployed on Amazon Bedrock AgentCore Runtime. Bedrock AgentCore Runtime validates the inbound JWT and, through Bedrock AgentCore Identity , issues a workload access token that binds the user and agent identities, and then invokes the agent. For queries requiring internal documents, the agent uses its AWS Identity and Access Management (IAM) role to query Amazon Bedrock Knowledge Bases (backed by an Amazon S3 vector store) with metadata filtering, and DynamoDB with user-scoped session-tagged credentials. For queries requiring external data, Bedrock AgentCore Identity retrieves credentials from AWS Secrets Manager and performs an on-behalf-of token exchange ( RFC 8693 ) with Salesforce, returning a user-scoped access token. The agent calls the Salesforce REST API using the user-scoped token. Salesforce applies sharing rules and returns only records the user is authorized to access. This architecture follows two key principles. The agent acts as an orchestrator, not a gatekeeper; it coordinates tool calls and reasoning but doesn’t control access to data. Authorization is enforced by downstream services. The agent doesn’t store credentials to data stores; instead, each request gets temporary, user-bound access tokens. In the following sections, we dive deep into each data source to show how these principles are achieved in practice. Initial user authentication with IdP When an employee opens the chat application, they authenticate using their corporate credentials. For this example, you use Amazon Cognito user pools as the IdP. You can also achieve this with other IdPs such as Entra ID or Okta. The pre token generation Lambda trigger (V2) captures the user’s custom department context and adds it to the tokens to both the identity (ID) token and access token that Bedrock AgentCore Runtime uses for authorization decisions each serving a distinct purpose. The access token is used by the Bedrock AgentCore Runtime custom JWT authorizer for inbound authorization. The ID token also receive the https://aws.amazon.com/tags claim (used by AWS Security Token Service (AWS STS)) for session tags). The https://aws.amazon.com/tags claim is the specific format required by AWS STS to extract session tags during AssumeRoleWithWebIdentity . For more information and step-by-step guidance see How to customize access tokens in Amazon Cognito user pools . The following example shows the key logic within a pre token generation Lambda handler function configured as a trigger on your Amazon Cognito user pool. This code runs automatically when a user authenticates, extracting their department attribute and adding it as a custom claim to both ID Token and access token. import json def lambda_handler(event, context): department = event['request']['userAttributes'].get('custom:department', '') event['response']['claimsAndScopeOverrideDetails'] = { 'idTokenGeneration': { 'claimsToAddOrOverride': { 'department': department, 'https://aws.amazon.com/tags': { "principal_tags": {"department": [department]}, "transitive_tag_keys": ["department"] } } }, 'accessTokenGeneration': { 'claimsToAddOrOverride': { 'department': department } } } return event Inbound authorization by AgentCore Runtime When the user request reaches AgentCore Runtime, the Inbound JWT authorizer performs two checks as shown in Figure 2. It validates the JWT token with Amazon Cognito (the configured IdP) by cryptographically verifying the token’s signature, confirming it is non-expired, and checking it was issued by the trusted IdP. It then extracts the department claim from the validated token and compares it against the expected value configured in the authorizer, any token without a matching claim is rejected before the agent code is invoked. Figure 2: Inbound JWT authorization The following example shows the inbound JWT authorizer configuration that you pass when deploying your agent to AgentCore Runtime. This configuration tells AgentCore which IdP to validate against and which custom claim value to enforce for this agent. In this example, inboundTokenClaimName is department, inboundTokenClaimValueType declares the claim type as STRING_ARRAY , and authorizingClaimMatchValue specifies the allowed values ( [“Sales”, “Finance”] ) with the CONTAINS_ANY operator. The authorizer validates that the department claim is present in the token and matches one of these values, ensuring only authenticated users from the Sales or Finance department can invoke the agent. authorizer_config = { "customJWTAuthorizer": { "discoveryUrl": discovery_url, "allowedClients": [client_id], "customClaims": [ { "inboundTokenClaimName": "department", "inboundTokenClaimValueType": "STRING_ARRAY", "authorizingClaimMatchValue": { "claimMatchValue": ["Sales", "Finance"] "claimMatchOperator": "CONTAINS_ANY" } } ] } } Note: AgentCore Runtime automatically creates a workload identity for each deployed agent. A workload identity represents the digital identity of your agents within the AWS environment. It allows agents to maintain consistent identity whether they’re using IAM roles for AWS resource access, OAuth 2.0 tokens for external service integration, or API keys for third-party tool access. Passing the user context for agent outbound authorization After the inbound JWT token is validated and the user’s authorization context is confirmed, the agent must propagate this context to downstream resources. The fundamental security challenge here is how to design a system so that an agent acting on behalf of a user can only access data that user is authorized to see, even if the agent itself is compromised. The traditional approach of granting the agent broad credentials and relying on application-level filtering (such as adding WHERE clauses to queries) creates a single point of failure. If an attacker manipulates the agent through prompt injection or exploits a bug in the filtering logic, the full dataset becomes accessible. A more resilient design moves authorization enforcement out of the agent’s application code and into the infrastructure layer wherever possible. Instead of trusting the agent to filter results correctly, you configure the underlying services—IAM policies, database access controls, SaaS sharing rules—to reject unauthorized requests regardless of what the agent asks for. This way, the agent’s credentials are inherently limited to the requesting user’s permissions, and no amount of prompt manipulation can bypass those boundaries. Where infrastructure-level enforcement isn’t yet available, such as metadata filtering in Amazon Bedrock Knowledge Bases, the agent applies application-layer controls as a complementary measure. The following sections demonstrate how this principle applies to each data source in our architecture. Pattern 1: Scoping DynamoDB access to the requesting user For DynamoDB access, you can use AssumeRoleWithWebIdentity with session tags to create per-request, user-scoped credentials rather than granting the agent a static IAM role with direct table access. The agent passes the user’s signed ID token to AWS STS, which extracts the department tag from the token’s https://aws.amazon.com/tags claim and returns temporary credentials constrained to that department’s data partition. This moves access control from agent code to IAM policy evaluation. STS additionally validates the token’s audience (aud) claim against the IAM OIDC provider configuration, preventing tokens issued for other app clients from being used to assume the role. The following diagram shows this flow (Figure 3). Figure 3: DynamoDB access using AssumeRoleWithWebIdentity and session tags Prerequisites (one-time setup): Before this runtime flow can execute, complete the following configuration: Register Amazon Cognito as an IAM OIDC provider. Although the user authenticates using the Cognito API ( USER_PASSWORD_AUTH ), STS requires Cognito to be registered as an OIDC provider so it can discover and validate ID tokens. Configure the allowed client IDs (audiences) on the provider to match your application’s app client ID. CognitoOIDCProvider: Type: AWS::IAM::OIDCProvider Properties: Url: !Sub 'https://cognito-idp.${AWS::Region}.amazonaws.com/${CognitoUserPoolId}' ClientIdList: - !Ref CognitoAppClientId ThumbprintList: - '<thumbprint>' Configure the UserScopedDynamoDBRole trust policy to include both sts:AssumeRoleWithWebIdentity and sts:TagSession permissions, with the Amazon Cognito OIDC provider as the federated principal. { "Version": "2012-10-17", "Statement": [{ "Effect": "Allow", "Principal": { "Federated": "arn:aws:iam::111122223333:oidc-provider/cognito-idp.us-east-1.amazonaws.com/us-east-1_EXAMPLE" }, "Action": [ "sts:AssumeRoleWithWebIdentity", "sts:TagSession" ], "Condition": { "StringEquals": { "cognito-idp.us-east-1.amazonaws.com/us-east-1_EXAMPLE:aud": "<app-client-id>" } } }] } By default, AgentCore Runtime drops custom headers as a security measure. To allow the X-Id-Token header through to the agent container, configure it in the agent runtime’s requestHeaderAllowlist so the ID token is forwarded to agent code. The following configuration tells AgentCore Runtime to forward only the X-Id-Token header to agent code, dropping other non-standard headers: request_header_config = { 'requestHeaderAllowlist': ['X-Id-Token'] } How it works: The user navigates the web application. The user authenticates with Amazon Cognito using USER_PASSWORD_AUTH . The JWT is issued with a custom department claim and the https://aws.amazon.com/tags claim for STS session tagging (covered in the preceding Initial user authentication with IdP section). Amazon Cognito returns the enriched tokens to the frontend. The access token carries the department claim for inbound authorization. The ID token carries both the department claim and the https://aws.amazon.com/tags claim for downstream STS calls. The user asks the agent a question (for example, “Show Q4 sales pipeline”). The frontend calls AgentCore Runtime, passing two tokens: the Amazon Cognito access token in the Authorization header (for inbound authorization), and the user’s ID token as a custom X-Id-Token header (for downstream STS calls). AgentCore Runtime validates the JWT and verifies the department claim matches the allowed values configured in the inbound authorizer. If validation fails, the request is rejected with HTTP 401 before agent code executes. After validation, AgentCore forwards the request to the agent container along with the allowed X-Id-Token header. The agent calls sts:AssumeRoleWithWebIdentity with the ID token. This call targets a single shared UserScopedDynamoDBRole . The following is the agent code for this step: def _scoped_dynamodb_resource(id_token: str): """Assume user-scoped role and return DynamoDB resource.""" sts = boto3.client('sts') response = sts.assume_role_with_web_identity( RoleArn=USER_SCOPED_DYNAMODB_ROLE_ARN, RoleSessionName="agent-user-session", WebIdentityToken=id_token, DurationSeconds=900 ) creds = response['Credentials'] session = boto3.Session( aws_access_key_id=creds['AccessKeyId'], aws_secret_access_key=creds['SecretAccessKey'], aws_session_token=creds['SessionToken'] ) return session.resource('dynamodb') AWS STS validates the token against the Amazon Cognito OIDC provider registered in IAM. STS verifies the token’s cryptographic signature, expiration, issuer, and audience ( aud ). The aud claim in the ID token must match one of the client IDs configured on the IAM OIDC provider resource. This prevents a valid token issued by the same Cognito user pool but for a different app client from being accepted. Note that the agent’s own execution role has no DynamoDB access and only permits sts:AssumeRoleWithWebIdentity , so even a compromised agent can’t bypass this flow. Note: Amazon Cognito user pools expose a standard OpenID Connect discovery endpoint, which is what you register as the trusted OIDC provider in IAM, even though the user signs in through the Cognito authentication APIs. When STS validates the token, it checks that the aud claim matches the client ID configured in the IAM OIDC provider. Tokens whose audience doesn’t match are rejected, adding a second control alongside signature and issuer validation. AWS STS extracts the https://aws.amazon.com/tags claim and creates a session with aws:PrincipalTag/department set. The trust policy’s sts:TagSession permission (configured in the prerequisites) enables this. Without it, STS silently drops the session tags and subsequent access is denied. AWS STS returns temporary credentials. These credentials are user-scoped and tamper-proof because the session tags are derived from the cryptographically signed JWT, not from agent code. The agent queries DynamoDB using these credentials. IAM evaluates the dynamodb:LeadingKeys condition against ${aws:PrincipalTag/department} . Only the user’s department partition is accessible. Because IAM evaluates this condition at the policy level, even if agent code is manipulated using prompt injection, cross-department access is denied. The following is an example of the permission policy on the role: { "Version": "2012-10-17", "Statement": [{ "Effect": "Allow", "Action": ["dynamodb:GetItem", "dynamodb:Query"], "Resource": "arn:aws:dynamodb:us-east-1:111122223333:table/CustomerRecords", "Condition": { "ForAllValues:StringEquals": { "dynamodb:LeadingKeys": ["${aws:PrincipalTag/department}"] } } }] } DynamoDB returns only the records from the user’s authorized department partition. Cross-department data is never returned because the IAM policy blocks the API call itself. It doesn’t rely on post-query filtering. The agent receives the authorized results and passes them to the LLM for natural language response composition. The composed response is returned to the frontend application and displayed to the user. Pattern 2: User-scoped authorization to Amazon Bedrock Knowledge Bases For documents stored in Amazon Bedrock Knowledge Bases, the agent applies metadata filtering at query time. Each document is tagged with a Department metadata attribute during ingestion. Amazon Bedrock Knowledge Bases using metadata filtering to implement the data authorization. You need to provide metadata files alongside the source data files with the same name as the source data file and .metadata.json suffix while uploading data in Amazon S3. Amazon Bedrock Knowledge Bases ingests these documents along with corresponding metadata file. The metadata attributes are stored alongside the vectors as filterable fields in the index. Each metadata file contains a simple JSON structure with the department attribute. The following example shows the complete content of a metadata file for Sales department documents: {"metadataAttributes": {"Department": “Sales"}} When the agent queries Amazon Bedrock Knowledge Bases, it calls the bedrock:Retrieve action and appends the retrievalConfiguration filter scoped to the user’s department. The department value is extracted from the JWT access token that the agent received during inbound authorization. response = client.retrieve( knowledgeBaseId=KNOWLEDGE_BASE_ID, retrievalQuery={"text": user_query}, retrievalConfiguration={ "vectorSearchConfiguration": { "filter": {"equals": {"key": "Department", "value": department}} } } ) Note: Metadata filtering is application-layer enforcement. The bedrock:Retrieve API doesn’t expose metadata filter content as an IAM condition key. For stricter isolation, consider separate knowledge bases per department with IAM resource-level policies. Pattern 3: User-scoped access to external services using on-behalf-of token exchange We use Salesforce as an example of an external service integration. The same on-behalf-of (OBO) token exchange pattern applies to external service that supports RFC 8693 or a compatible token exchange mechanism. External services like Salesforce don’t support IAM-based access control, so you need a different mechanism to propagate user identity. The AgentCore Identity OBO token exchange (RFC 8693) provides this by exchanging the user’s authenticated identity for a user-scoped token that the external service will recognize and enforce natively. AgentCore Identity supports three OAuth patterns for external service access. With client credentials—Two-Legged OAuth (2LO) or machine-to-machine (M2M)—the agent authenticates as a service account and receives a token with broad access. The agent is then responsible for filtering data in queries, which makes this pattern suitable when accessing organization-wide data that isn’t scoped to an individual user. A variation of this pattern embeds user context as custom claims within the agent’s M2M token itself, see Empower AI agents with user context using Amazon Cognito . With Authorization Code (3LO), the user explicitly consents through a browser redirect and the external service enforces per-user access. This works when per-service consent is required, but it demands user interaction during the flow, making it impractical for background agent operations. Learn more about this in Secure AI agents with Amazon Bedrock AgentCore Identity on Amazon ECS . With OBO token exchange, the user’s already-authenticated identity is exchanged for a service-scoped token without any additional user interaction, and the external service enforces access. For this use case, OBO is the most appropriate pattern. The user has already authenticated at the entry point (through the IdP), and the agent needs to act on their behalf across multiple services without prompting for additional consent. OBO propagates user identity end-to-end without the agent holding credentials, scales automatically with no per-user token storage, and allows downstream services to enforce their own authorization (sharing rules, role-based access control (RBAC)). Because no browser redirect is needed, OBO works seamlessly for background tool calls where the user isn’t present in a browser session. Figure 4 demonstrates the complete flow when using OBO token exchange. Figure 4: End-to-end user authorization flow for external access How it works: The user navigates to the web application. The user authenticates with Amazon Cognito using USER_PASSWORD_AUTH . A pre token generation Lambda function injects the custom department claim into the token (covered in the preceding Initial user authentication with IdP section). Amazon Cognito returns the tokens to the frontend. The access token is issued with the department claim. The user asks the agent a question (for example, “Show me Sales opportunities”). The frontend calls AgentCore Runtime with a single agent Amazon Resource Name (ARN), passing the Amazon Cognito access token: POST /invocations, Authorization: Bearer {access_token} . AgentCore Runtime validates the inbound JWT (signature, expiration, issuer, and custom claims including the department claim). After successful validation, AgentCore Runtime extracts the user identity from the JWT and calls the GetWorkloadAccessTokenForJWT API to exchange it for a workload access token . The agent code receives the workload access token through the invocation payload header. Workload access tokens are exclusively for accessing Amazon Bedrock AgentCore services and can’t be used directly for external services. The agent calls AgentCore Identity ( GetResourceOauth2Token ) with the workload access token, requesting a Salesforce token through the configured OBO (on-behalf-of) credential provider. AgentCore Identity validates the caller identity and agent identity, then accesses the stored client credentials from Secrets Manager. If a previously stored OAuth access token has expired, AgentCore Identity automatically obtains a new one using the client credentials, reducing the need for manual token lifecycle management in agent code. The agent code uses the @requires_access_token decorator to invoke this flow: @requires_access_token( provider_name="salesforce-token-exchange", scopes=[], auth_flow="ON_BEHALF_OF_TOKEN_EXCHANGE", ) def _get_salesforce_token_sync(*, access_token: str) -> str: return access_token On the AWS side, this requires an AgentCore Identity OAuth Client configured with Grant type: Token Exchange , Actor token: None , pointing to the Salesforce token endpoint. The Salesforce Connected App consumer secret is stored in Secrets Manager (the agent doesn’t access it directly). AgentCore Identity performs RFC 8693 token exchange with the Salesforce token endpoint, sending the user identity as the subject_token . AgentCore Identity performs this secure token exchange for user-delegated access based on the configured OAuth 2.0 credential provider. The agent can’t request tokens for arbitrary users because the workload access token cryptographically binds the request to the authenticated user. Salesforce validates the token against the registered Amazon Cognito auth provider configured in Salesforce Setup. Salesforce resolves the user using FederationIdentifier . On the Salesforce side, this requires: Amazon Cognito registered as an OpenID Connect auth provider A token exchange handler (Apex class extending Auth.Oauth2TokenExchangeHandler ) that resolves users by FederationIdentifier Token exchange flow enabled on the connect app or external client app Each user’s FederationIdentifier set to their Amazon Cognito subject’s ( sub ) unique user identifier (UUID). Sharing rules configured to enforce department-scoped record access The federation ID ( sub ) is immutable and can’t be spoofed by the agent, because it originates from the cryptographically signed identity token. Salesforce returns a user-scoped access token to AgentCore Identity, which passes it back to the agent. Agent calls the Salesforce REST API using the user-scoped token. No department filtering is needed in the Salesforce Object Query Language (SOQL) query because Salesforce enforces access through sharing rules: @tool def query_salesforce_opportunities(query_text: str) -> str: access_token = _get_salesforce_token_sync() # No department filter needed. Salesforce sharing rules enforce access. soql = "SELECT Id, Name, Amount, StageName, CloseDate FROM Opportunity ORDER BY CloseDate DESC LIMIT 10" response = requests.get( f"{SALESFORCE_URL}/services/data/v59.0/query?q={urllib.parse.quote(soql)}", headers={"Authorization": f"Bearer {access_token}"}, timeout=30, ) return json.dumps(response.json().get("records", [])) Salesforce applies sharing rules and returns only records the user is authorized to access. The agent doesn’t hold Salesforce credentials (refresh tokens, client secrets), these remain with AgentCore Identity. The agent’s LLM composes a response from the returned records. The frontend displays the results to the user. Conclusion In this post, you learned how to enforce consistent, end-to-end authorization in agentic AI applications by propagating user context from Amazon Cognito through Amazon Bedrock AgentCore to downstream resources. We showed you three patterns: Per-request user-scoped credentials using AssumeRoleWithWebIdentity with session tags, evaluated by IAM attribute-based access control (ABAC) policies to access Amazon DynamoDB Department-scoped metadata filtering at the application layer to access Amazon Bedrock Knowledge Bases. On-behalf-of token exchange (RFC 8693) using AgentCore Identity, with Salesforce-native sharing rules governing access to external CRM data. The key takeaway is that the agent coordinates work but doesn’t decide who can access what. Access decisions are made by infrastructure-level controls and the downstream service’s authorization model. This layered approach means that even if the agent behaves unexpectedly, unauthorized data access is still blocked. You can use this as a reference implementation and adapt it to your requirements by choosing authorization attributes relevant to your organization (such as department, role, business unit, or region), integrating additional data sources, or extending the token exchange patterns to other external services. Next steps Explore the sample code sample-authorization-context-with-agentcore for the complete reference implementation For a deeper overview of workload identities and credential management, see Securing AI agents with Amazon Bedrock AgentCore Identity For the Authorization Code (3LO) pattern on self-hosted compute, see Secure AI agents with Amazon Bedrock AgentCore Identity on Amazon ECS For M2M token customization with embedded user context, see Empower AI agents with user context using Amazon Cognito For IAM scoping patterns in Model Context Protocol (MCP)-based agent architectures, see Secure AI agent access patterns to AWS resources using MCP . For agent identity and permission management best practices, see AGENTSEC03 in the AWS Well-Architected Agentic AI Lens If you have feedback about this post, submit comments in the Comments section below. Anshu Bathla Anshu is a Sr. Lead Consultant – Security at AWS, based in Gurugram, India. He works with customers across diverse verticals to help strengthen their security infrastructure and achieve their security goals. Outside of work, Anshu enjoys reading books and gardening at his home garden. Connect with him on LinkedIn . Prafful Gupta Prafful is a DevOps Engineer at AWS, based in Gurugram, India. Having started his professional journey with Amazon, he specializes in DevOps and generative AI solutions, helping customers navigate their cloud transformation journeys. Beyond work, he enjoys networking with fellow professionals and spending quality time with family. Connect with him on LinkedIn . Rohit Verma Rohit is a Delivery Consultant – Security, Risk and Compliance at AWS, based in Gurugram, India. He partners with customers across multiple industries to strengthen their security posture, leading risk consulting engagements, and security deliverable reviews. Outside of work, Rohit is a fitness enthusiast who enjoys music and reading non-fiction books. Connect with him on LinkedIn .
aws.amazon.comAug 19, 2026extracted
Password spraying attacks surge 155x as hackers exploit MFA gaps
Huntress has observed a 155x increase in password spraying attacks in the first half of 2026. Brute force is old news, but the spin driving that spike is new. One major contributor was a campaign targeting Microsoft's Azure CLI, the command-line tool admins use to manage Azure and Entra resources. The traffic originated from an IPv6 range controlled by internet hosting provider LSHIY LLC. The campaign started months earlier, but in mid-June alone Huntress observed more than 81 million related login attempts and 78 account compromises in a two-week window. The auth flow that time forgot A typical password spraying attack follows a familiar pattern: 1. Reconnaissance: The attacker collects valid usernames via LinkedIn, company websites, data breach dumps, and phishing to create a target list. 2. Build password list: The attacker assembles a short list of breached passwords, common passwords such as "Password123," company name variants, or seasonal terms. 3. Spray across accounts: The attacker tries one password against every account on the target list. Heeding lockout thresholds, they wait before moving to the next password in a low and slow approach. 4. Gain a foothold: If granted access, the attacker pivots to lateral movement, business email compromise (BEC), data exfiltration, or further credential theft. The LSHIY campaign combined password-spraying scale with the reuse of valid username-and-password pairs from previous breaches that were never rotated. That made each successful attempt more valuable than a typical guess. The attacker also abused Resource Owner Password Credentials (ROPC), a legacy OAuth grant deprecated in OAuth 2.1. ROPC was introduced to help applications migrate from direct authentication schemes to OAuth. ROPC doesn’t support modern authentication flows like MFA or SSO. Instead, it sends the username and password straight to the /token endpoint, with no interactive MFA prompt. For an attacker, a reused password that still works can become an active session. This matters because many of the compromised businesses had implemented multi-factor authentication (MFA) via a Conditional Access Policy (CAP), but the MFA was not configured to cover this specific flow that attackers used. As Andrew “Spike” Brandt, Principal Threat Intelligence Incident Commander at Huntress, put it: “Even though we call it an authorization method, it’s technically an impersonation method.” Huntress saw no post-compromise activity after the successful logins tied to the LSHIY campaign. Rich Mozeleski, Staff Product Manager at Huntress, suspects the attacker may have been validating credentials for resale on the dark web. LSHIY later terminated the attacks from the original IP range and confirmed that the attacker had been using its bring-your-own-IP (BYOIP) offering. Hacker tradecraft’s evolving daily, so let’s break it down on Tradecraft Tuesday! Join us monthly for an in-depth look at attacker tradecraft—no sales or product talk involved. Sign up for the series today or catch up on previous episodes. No tricks, just tradecraft. Register for Tradecraft Tuesday It’s an IPv6 BYOIP party BYOIP is a legitimate service that lets an ISP's customers route traffic through the provider using IP ranges they own themselves. BYOIP lets attackers move between IP ranges and providers, complicating blocking and detection. That flexibility can help attackers evade IP-based detection and account-lockout controls. Attacks from the LSHIY campaign originated from IPv6 range 2a0a:d683::/32. IPv6 gives attackers an enormous pool of addresses to work with, making it harder for defenders to rely on blocking a small set of IPs. After LSHIY shut down the original activity, the spray attempts first shifted to FranTech-hosted IPv6 ranges. Subsequent activity appeared from 3xK Tech using IPv4. The ease of switching providers turns infrastructure blocking into a familiar whack-a-mole problem for defenders. These arrangements are easy to swap between providers, which creates a familiar "whack-a-mole" threat hunting scenario for defenders. Scope is the soft spot The LSHIY campaign doesn’t appear to target a particular industry. Instead, it takes advantage of organizations where password controls or multi-factor authentication (MFA) policies leave gaps attackers can exploit. Huntress analyzed 23 affected businesses. Eight had no MFA in place. Of the remaining 15, MFA didn’t apply to the attacker’s sign-in attempts because policies were limited to certain apps or user groups, relied on trusted locations, or remained in report-only mode. The findings show that even with MFA, organizations need to review how their Conditional Access policies are scoped and enforced. A policy can appear to require MFA while still leaving out specific users, applications, or sign-in methods. Fine-tuning conditional access without locking out legitimate users is hard, and that difficulty is part of why this keeps working for attackers. Shut off the tap The following mitigation strategies close the gaps these attacks rely on: Enforce password hygiene, consider passwordless options Disable ROPC (or apps that rely on it) from your system Restrict the Azure CLI application for non-admin users Don't prioritize response by spray volume, since the most heavily sprayed tenants are often the least compromised. Prioritize by credential validity instead. Require MFA for all users, all cloud apps, and all client app types, with no exclusions. Block authentication methods that can’t satisfy an MFA requirement, including the legacy ROPC grant. Use a strong Conditional Access setting like userStrongAuthClientAuthNRequired to enforce strong authentication at the client level and block ROPC. As Mozeleski put it, "Appropriately configured and managed conditional access is a superpower." Attackers can switch providers and IP ranges faster than defenders can block them. Shut this down by making sure a password alone cannot open the door: keep passwords strong, limit Azure CLI access to people who need it, and apply Conditional Access across all users, cloud apps, and client app types. Tradecraft Tuesday: No Products. No Pitches. Just Hacks. Tradecraft Tuesday provides cybersecurity professionals with an in-depth analysis of the latest threat actors, attack vectors, and mitigation strategies. Each weekly session features technical walkthroughs of recent incidents, comprehensive breakdowns of malware trends, and up-to-date indicators of compromise (IOCs). Participants gain: Detailed briefings on emerging threat campaigns and ransomware variants Evidence-driven defense methodologies and remediation techniques Direct interaction with Huntress analysts for incident response insights Access to actionable threat intelligence and detection guidance Advance your defensive posture with real-time intelligence and technical education specifically designed for those responsible for safeguarding their organization’s environment. Sponsored and written by Huntress Labs.
bleepingcomputer.comAug 19, 2026extracted
Your polite reply to that text is worth $2 on the dark web
Most wrong-number texts are harmless. Some are the first step in a carefully planned scam. By replying, you may be confirming that your number is active and that you’re willing to engage with strangers, making you a more valuable target for future fraud. Here’s why a polite response can be worth money to cybercriminals.  The politeness trap  Sunday night. You’re on the couch, half-watching Netflix, when your phone buzzes.  “Hey! Are we still on for dinner tomorrow? Don’t forget the wine ”   You don’t recognize the number. You glance at it for two seconds, then type what most polite people would:  “Sorry, I think you have the wrong number!”   You put your phone down. Go back to Netflix, and forget about it within five minutes.  On the other end, though, your reply has just told the sender something valuable. Not because of a technical exploit or an invisible cyber-attack, but because you just proved you’re the kind of person who responds to strangers politely.  According to cybercrime intelligence reports, responsive phone numbers are worth significantly more than inactive ones. With a single reply, you’ve entered a global criminal ecosystem run by transnational syndicates that, according to analysts , moves tens of billions of dollars.   What your reply told them  Let’s be clear: the “wrong number” text is not a phishing link. It’s not malware. In many cases, it’s not even the scam itself. It’s a personality test.   The scammers already have your number. They may have bought it in bulk from a data breach for a fraction of a cent per record. They already know the message was delivered because their SMS gateway received no delivery failure. Text messages remain one of the most effective ways to reach people, with exceptionally high open rates and most being read within minutes. That’s one reason scammers prefer SMS to email.  What they don’t know is whether you’re worth spending more time on. Your reply told them three useful things:   You’re responsive. You saw the message and felt compelled to reply. This immediately places you in their top 15–20% most active numbers category.   You’re polite. You didn’t ignore it and didn’t respond aggressively. You wanted to help a stranger. Scammers deliberately exploit that instinct to be polite and helpful.   You reply quickly. The time between their message and your reply can reveal how closely you monitor your phone, help estimate your timezone, and indicate how likely you are to respond to future messages. The two paths your number takes  From this moment, your story splits. Both paths described below play out across millions of phones worldwide.  Scenario A: The slow burn  Within minutes of your reply, another message arrives in response to yours:  “Oh no, I’m so sorry! But honestly, you seem like a really kind person. It’s rare to find polite people these days. I’m Sarah, by the way.”    Some people stop the conversation there. Others reply out of curiosity or because they’re simply being friendly. A few messages later, you’re in a conversation.  In some large scam operations, those early exchanges may be handled by AI (Artificial Intelligence) using open-source language models such as Llama or Mistral. That allows scammers to hold thousands of conversations at once and focus their time on the people who seem most likely to keep talking.   While keeping you engaged, the AI assigns you a real-time vulnerability score based on your response time and message length. If your score crosses a certain threshold, a human operator takes over. They read the conversation, learn your name, your job, and your communication style, then continue as though nothing has changed.  Within two or three weeks, this person has become a friend. They text you good morning, ask about your day, and send photos stolen from real social media profiles.  Around week three, they casually mention an investment:   “I’ve been making really good money on an investment platform lately. Almost $4,000 last month. It’s crazy.” If you show interest, they’ll send you a link to a fake trading platform with a convincing design. You might deposit $500 to test it. The next day, your dashboard shows a fake gain of $1,800, so you invest more. A week later, the platform disappears, along with your money, and the person who texted you every day.  According to the FBI’s Internet Crime Complaint Center (IC3), investment fraud generated more than $4.5 billion in reported losses in a single year. To be clear: while most wrong-number texts never reach this stage, victims who fall for so-called “pig butchering” scams (long-term romance/financial scams) suffer catastrophic average losses ranging between $70,000 and $75,000 per person.  Scenario B: The silent recycling  In this scenario, you replied “wrong number” and never heard from them again. You think you dodged the scam, but instead your number was simply moved to a different category: “Active, responsive, polite, but not susceptible to the wrong-number hook.”  That profile still has enormous commercial value. Your number is added to a cleaned database and sold or reused for a different campaign.   A week later you receive a text from another number:   “Hi! I saw your profile on LinkedIn. We have an opportunity that’s a perfect fit for your background.”   Or:  “Your package couldn’t be delivered, update your address by clicking here.”   Or a fake alert from your bank warning of “suspicious activity.”  You’ll probably never connect these messages to the wrong-number text you received the week before. They’re different topics and different senders. But they may all be part of the same criminal ecosystem. The first message was simply a way to sort potential targets. Everything that follows is the actual attack.  The most common hooks  If you’ve received one of these messages (or something very similar), you’re not alone. These are some of the most common opening lines used in wrong-number scams, tested on millions of people and optimized to maximize response rate:  The friend who doesn’t exist:   “Hey! See you tonight at 6? Don’t be late ”  “Are you still free tomorrow?”  “Did you send those files to the office?” “Hey Marco, are we still on for dinner tonight?”  The concerned neighbor:  “Sorry to bother you, I’ve noticed your dog sometimes runs into my yard.”  “I found a phone number on the dog tag, is this yours?”  “Hi, your package was delivered to my address by mistake.”  The professional mix-up:  “Hi, I tried to reach you about the delivery but you didn’t answer.”  “The shipment arrived at your address, can you confirm?”  “This is Mike from the office, did you get my earlier message?”  The family emergency:  “Do you know Sarah? There’s been an emergency.”  “Is this [common name]’s number? Something happened.”  The recruiter:  “Hi! I came across your profile, we have an incredible opportunity.”  “Hey, I’m reaching out about a position that matches your background perfectly.” If you’ve received one of these messages, it doesn’t automatically mean it’s a scam. People genuinely do text the wrong number sometimes. But if the conversation quickly moves to making small talk, asking personal questions, or encouraging you to keep chatting, stop replying.  Don’t recognize that number? We’ll check it. CHECK NOW The crime industry behind the text  These messages aren’t usually sent by a lone cybercriminal. They’re part of a highly organized criminal industry with its own market dynamics and global supply chains.  In January 2026, Cambodian and Chinese authorities arrested Chen Zhi, president of Prince Holding Group, accusing him of running a network of scam compounds across Southeast Asia where thousands of trafficked people were forced to manage these conversations. Those operations relied on underground marketplaces where criminals could buy everything they needed, from phone lists and stolen identities to AI tools and fake investment websites.  The scale is staggering. Blockchain analytics firm Elliptic estimates the Huione Guarantee underground marketplace processed more than $134 billion in transactions. Separately, researchers at the University of Texas at Austin estimate that pig-butchering scams stole more than $75 billion in cryptocurrency over four years.   The scam funnel: Costs and revenue  To understand why this ecosystem is so huge, look at the math. Sending hundreds of thousands of text messages costs very little. Even if only a tiny fraction of people reply, and an even smaller number eventually send money, the profits can far outweigh the costs.   Look at this illustrative model of a campaign sending 100,000 SMS messages:  The figures in this model aren’t arbitrary. They combine observed pricing from underground marketplaces such as Russian Market and BidenCash with average victim losses reported by law enforcement agencies, including the FBI’s Internet Crime Complaint Center (IC3).   Even allowing for variation between campaigns, the economics are compelling. A single campaign can cost less than $1,000 to run while generating more than $200,000 in revenue, representing a potential return on investment (ROI) of 90x to 200x.  Those same economics are reflected in underground marketplaces, where verified, enriched contact details command significantly higher prices than raw data. In our previous investigation into underground marketplaces , we found that a typical stolen personal record sold for around 95 cents. The more criminals learn about a potential victim, the more valuable that person’s data becomes.  The price ladder of your phone number:  .kb-table-container445707_d29b97-2a{overflow-x:auto;}.kb-table445707_d29b97-2a tr > *:nth-child(2){width:21%;}.kb-table445707_d29b97-2a{table-layout:fixed;width:100%;}.kb-table445707_d29b97-2a tr{height:0px;}.kb-table-container .kb-table445707_d29b97-2a th{padding-top:var(--global-kb-spacing-xxs, 0.5rem);padding-right:var(--global-kb-spacing-xxs, 0.5rem);padding-bottom:var(--global-kb-spacing-xxs, 0.5rem);padding-left:var(--global-kb-spacing-xxs, 0.5rem);text-align:left;}.kb-table-container .kb-table445707_d29b97-2a caption{text-align:center;}.kb-table-container .kb-table445707_d29b97-2a td{padding-top:var(--global-kb-spacing-xxs, 0.5rem);padding-right:var(--global-kb-spacing-xxs, 0.5rem);padding-bottom:var(--global-kb-spacing-xxs, 0.5rem);padding-left:var(--global-kb-spacing-xxs, 0.5rem);text-align:left;}.kb-table-container .kb-table445707_d29b97-2a td, .kb-table445707_d29b97-2a th{border-top:2px solid #CCCAD7;border-right:2px solid #CCCAD7;border-bottom:2px solid #CCCAD7;border-left:2px solid #CCCAD7;}@media all and (max-width: 1024px){.kb-table-container .kb-table445707_d29b97-2a td, .kb-table445707_d29b97-2a th{border-top:2px solid #CCCAD7;border-right:2px solid #CCCAD7;border-bottom:2px solid #CCCAD7;border-left:2px solid #CCCAD7;}}@media all and (max-width: 767px){.kb-table-container .kb-table445707_d29b97-2a td, .kb-table445707_d29b97-2a th{border-top:2px solid #CCCAD7;border-right:2px solid #CCCAD7;border-bottom:2px solid #CCCAD7;border-left:2px solid #CCCAD7;}} .kb-table-container .kb-table tr.kb-table-row445707_c65fe3-3f{background-color:rgba(0,89,255,0.17);height:48px;} Lead Type   Price   What Triggers It   Raw phone number (unverified, from old breach)  $0.01 – $0.05  Your data leaked years ago  Confirmed active number  $0.50 – $2.00  You replied “wrong number”  Enriched with profile data (name, job, income estimate)  $1.00 – $5.00  OSINT scripts scraped your socials  “Hot lead” (psychologically vulnerable, lonely, engaged)  $6.00 – $10.00  You chatted for 3+ days, showed openness  That’s a  4,000% value increase  generated by a single polite reply.    From there, scammers can enrich that record with publicly available information such as your name, employer, social media profiles, and estimated demographics using automated open-source intelligence (OSINT) techniques.  The more complete the profile becomes, the more valuable it is. Researchers monitoring underground marketplaces have found that enriched, pre-profiled contacts command premium prices because they’re more likely to become victims of high-value pig-butchering scams that generate billions of dollars in illicit revenue each year. How do they know who you are?  Before that text reaches your phone, your number may already have passed through automated script pipelines capable of cross-referencing tens of thousands of records in minutes.  Acquisition : Your number is pulled from historical data breaches, such as the Facebook leak affecting 533 million users, Twitter/X data leaks, or massive aggregated databases like Naz.api, and the Mother of All Breaches (MOAB), a collection of more than 26 billion records compiled from thousands of previous breaches.  Automated scraping : Software queries public sources to check whether your number is linked to an active WhatsApp account, collect your profile information and picture and match the number to public LinkedIn, Instagram, and Facebook profiles.  Data broker integration : Scammers exploit the same commercial data services used by marketing companies to associate a phone number with estimated age, address, and income bracket.  The result is a psychographic and commercial profile that helps scammers choose the most convincing approach. If your social media shows you have a dog, you might receive the neighbor hook: “Your dog keeps getting into my yard.” If you recently changed jobs on LinkedIn, the fake headhunter hook activates.  The human factor: Modern slavery  There’s one aspect of these scams that’s often overlooked: many of the people sending the messages are victims themselves.  In its August 9, 2023 policy report , the United Nations Office on Drugs and Crime (UNODC) described a human rights crisis tied to forced criminality in Southeast Asia. It estimates at least 120,000 people in Myanmar and tens of thousands in Cambodia are being held in fortified mega-compounds run by criminal syndicates.  Many were lured by fake job adverts promising legitimate work in digital marketing or customer service. Once they cross the border, their passports are confiscated. They were stripped of freedom and forced, under the threat of violence, to spend up to 16 hours a day managing dozens of scam conversations. Those who failed to meet financial targets were often beaten, isolated, or sold to other compounds.  When you reply to one of these messages, you’re interacting with a system designed to simultaneously exploit your financial availability and the enslavement of another human being.  Breaking the chain  You can’t erase your number from dark web databases: that damage may have done years ago. But you can make your profile far less valuable to scammers.  Make yourself harder to profile : Review the privacy settings on any messaging apps and social media platforms that use your phone number. Limit who can see information such as your profile photo, status, last seen, and phone number. The less information scammers can gather automatically, the harder it is to build a detailed profile about you. On WhatsApp, for example, you can set Profile Photo , About , Status , and Last Seen to My Contacts . On Telegram, set Phone Number to Nobody .  Report before you block: Blocking protects only you. Reporting protects everyone. When you use WhatsApp’s Report and Block function, the last five messages in the chat are sent to Meta’s security teams. If enough people report the same number, it may be permanently banned, destroying the entire active campaign on that line.  The golden rule: If you receive an unexpected message from an unknown number, the safest response is no response at all . Don’t reply, don’t explain yourself, and don’t worry about seeming impolite. If it’s a genuine wrong number, the sender will usually realise their mistake and move on. If it’s a scam, you’ve denied the criminals exactly what they wanted: proof that your number is active and that you’re willing to engage.   Something feel off? Check it before you click.    Malwarebytes Scam Guard  helps you analyze suspicious links, texts, and screenshots instantly.   Available with  Malwarebytes Premium Security  for all your devices, and in the  Malwarebytes app for iOS and Android .   Try it free →  
malwarebytes.comAug 19, 2026extracted
Attackers Exploit MLflow SSRF Flaw to Steal Cloud Credentials and Secrets
Two critical vulnerabilities impacting MLflow, an open-source artificial intelligence (AI) platform, and FUXA, an open-source, web-based SCADA / HMI software built for operational technology (OT) and industrial automation, are witnessing malicious scanning and exploitation efforts. According to independent reports from watchTowr and VulnCheck, the vulnerabilities in question are as follows - CVE-2026-64849 (CVSS score: 9.3) - An unauthenticated Server-Side Request Forgery (SSRF) vulnerability in MLflow that can allow an attacker who can reach the Tracking Server (mlflow server) to issue HTTP requests to arbitrary internal cloud metadata endpoints and extract sensitive data. (Affects versions < 3.15.0) CVE-2026-25895 (CVSS score: 9.5) - A missing authentication for a critical function and path traversal vulnerability in FUXA that can allow an unauthenticated, remote attacker to write arbitrary files to the server file system and achieve remote code execution. (Affects versions <= 1.2.9) "Attackers are exploiting [CVE-2026-64849] to reach cloud metadata services directly, and exfiltrating cloud credentials and secrets," watchTowr said in a post on LinkedIn, adding it detected bad actors indiscriminately scanning for exposed MLflow instances online within hours of the CVE being assigned on August 17, 2026. "It allows an attacker to exploit a flaw in MLflow's model-registry webhooks to proxy requests through the affected system and interact with internal services," Yordan Ganchev, principal threat intelligence specialist at watchTowr, said in a statement shared with The Hacker News. "The security bug bypasses prior fixes because of how it handles web redirects. Evidence from our global honeypot telemetry indicates attackers are abusing this vulnerability to target cloud-hosted MLflow systems in an attempt to extract credentials and secrets from well-known internal IP addresses and services." Organizations running MLflow are recommended to prioritize patching affected, exposed systems, review audit logs for signs of compromise, and check whether sensitive credentials have been exposed. As for CVE-2026-25895, VulnCheck said it detected malicious scanning aimed at the flaw starting August 18, 2026. A single IP address has been observed broadly scanning the internet for vulnerable FUXA instances. There are about 60 FUXA installations exposed to the public internet. "The attacker request attempts to overwrite main.js with junk data via the CVE-2026-25895 path traversal," Caitlin Condon, vice president of research at VulnCheck, said in a LinkedIn post. "No RCE payloads dropped yet." Over the past year, two other vulnerabilities in FUXA – CVE-2026-25939 and CVE-2023-33831 – have also witnessed active exploitation efforts, with the latter witnessing activity "dating back to November 2025 and as recently as yesterday," per Condon.
thehackernews.comAug 18, 2026extracted
UNISOC Modem Flaw Enables Remote Code Execution via Video Calls
A vulnerability in UNISOC modem firmware can allow arbitrary code execution with kernel privileges from the modem context, potentially allowing an attacker to modify Android kernel code. The flaw stems from a lack of isolation between modem memory and kernel memory. This is according to new research by the SSD Secure Disclosure technical team, which was credited to independent security researcher 0x50594d. The firm demonstrated a full exploit chain in which modem-level code execution was extended into kernel-level execution. The issue has been identified in phones using UNISOC chipsets, with SSD listing the Xiaomi Redmi A5 with a January 1, 2026 security patch and the Motorola E13 with a February 1, 2025 security patch among affected devices. SSD classified the underlying flaw as Improper Isolation of Shared Resources on System-on-a-Chip (SoC), tracked as Common Weakness Enumeration (CWE) 1189. The researchers said the missing isolation allows code running in the modem context to access memory used by the Android kernel. Modem Isolation Failure Enables Kernel Access The vulnerability allows an attacker who has already gained code execution on the modem to disable protections on a Memory Protection Unit (MPU) region. This gives the modem context access to physical memory, including memory used by the Android kernel. SSD tested the full chain against a Realme C33 with an Android security update from July 2025. The disclosure links the test to a previously disclosed UNISOC T612 RCE and demonstrates the resulting execution of a payload in kernel space. The final stage was triggered by placing a video call to the target phone. The researchers used a Voice over Long-Term Evolution (VoLTE) connection in their test environment, demonstrating how modem-level execution could be extended to kernel-level code execution. No UNISOC Response Reported The disclosure does not identify a vendor firmware update addressing the flaw. SSD also does not present its listed devices as an exhaustive inventory of affected phones. For affected device owners, the disclosure leaves firmware updates from UNISOC and handset manufacturers as the key route to remediation. Similar risks have been demonstrated in other cellular modem components, including Cinterion modem vulnerabilities in 2024 that researchers said could allow remote attackers to execute arbitrary code and manipulate device memory. SSD said it attempted to contact UNISOC through email and LinkedIn. Infosecurity has also contacted UNISOC for comment but has not received a response at the time of writing. UNISOC (Shanghai) Technologies is a top-three global fabless semiconductor company headquartered in Shanghai, specializing in 2G/3G/4G/5G mobile communication, IoT and smart device chipsets.
infosecurity-magazine.comAug 17, 2026extracted
Unisoc VoLTE Video Call Exploit Chain Can Give Attackers Full Android Kernel Access
Security researchers at SSD Secure Disclosure have published a two-stage exploit chain that achieves full Android kernel access on devices running Unisoc modem firmware through a VoLTE video call, with no fix from the chipset maker. The advisory, published August 17, 2026, is the second stage of a chain that began in March 2026, when SSD disclosed remote code execution in the same firmware through a malformed SIP video call. Completing the full chain requires the attacker to control a private 4G cellular network and the victim to answer the incoming video call. "We have tried to reach out to the vendor through multiple channels (email and LinkedIn) but have not been able to receive any response," SSD Secure Disclosure said in its advisory. The March 2026 disclosure carried the same statement. The research was carried out by an independent security researcher using the handle 0x50594d. The privilege-escalation vulnerability is classified as CWE-1189, Improper Isolation of Shared Resources on System-on-a-Chip, and no CVE identifier has been assigned as of publication. The flaw resides in the modem firmware shared by at least three Unisoc chipsets, among them the T606 found in the Motorola E13, the T612 found in the Realme C33, and the T7250 found in the Xiaomi Redmi A5. Unisoc, a Shanghai-based chipmaker formerly known as Spreadtrum, supplies components to brands including Motorola, Realme, and Xiaomi for devices sold across more than 140 countries, according to the advisory. Researchers confirmed the privilege-escalation flaw on a Motorola E13 carrying a February 2025 security patch and on a Xiaomi Redmi A5 carrying a January 2026 patch. Running the complete chain requires a modem-level foothold from the March 2026 RCE vulnerability first, along with attacker-controlled VoLTE infrastructure and a victim who answers the incoming video call. The researchers built their proof-of-concept environment using an open-source 4G core network, a software-defined radio for the 4G radio interface, and specialized SIM cards. Once code is running on the modem, the privilege-escalation step works by writing a full-access configuration to the modem's ARM Memory Protection Unit through coprocessor registers, mapping the entire 32-bit physical address space as readable, writable, and executable from modem context, including the pages where the Android kernel resides. The condition making this possible is a shared physical memory space between the modem processor and the application processor within the Unisoc SoC, with no hardware-enforced boundary preventing modem-context code from modifying kernel memory. Researchers confirmed kernel-level code execution on a test device by observing kernel log output showing that the injected payload had run. The August 2026 Android Security Bulletin, published before this disclosure, does not address the privilege-escalation vulnerability, and no UNISOC security bulletin covers it. A separate UNISOC advisory from October 2025, CVE-2025-31718 (CVSS score: 7.5), describes a modem input-validation flaw on the same chipset family, though it's not clear whether it corresponds to the March 2026 SSD disclosure. Device owners currently have no available patch or mitigation and should watch for a firmware update from their device manufacturer. The disclosure follows independent research published in November 2025 by Kaspersky ICS CERT, which documented the same architectural condition on a different Unisoc chip, the UIS7862A, found in vehicle head units. After gaining modem code execution via a separate vulnerability, the Kaspersky team was also able to reach and modify the running Android kernel by exploiting the modem and application processor's shared physical address space. Kaspersky described one of its lateral movement paths, involving a hidden Direct Memory Access peripheral, as a hardware-level issue not fixable through a software update. The Memory Protection Unit route used in the SSD chain is in principle addressable through a firmware change, though no such update has been committed to by UNISOC. A coordinated Unisoc modem vulnerability uncovered by Check Point Research in 2022, CVE-2022-20210, was patched by UNISOC and distributed through the Android Security Bulletin. The two currently disclosed vulnerabilities carry no such assurance.
thehackernews.comAug 17, 2026extracted
How Anthropic plans to watermark Claude's AI-generated text
It could soon become easier to identify AI-generated content, even if it's not the usual "It's Not X, it's Y" type of post you'd come across on LinkedIn and other socials. As you may be aware, the EU now requires AI companies serving its market to mark their AI-generated content so it's easier to identify. Anthropic and several other major AI providers have agreed to comply with the EU's Code of Practice, with Anthropic becoming one of the first companies to share details about how it will implement watermarking across Claude. Anthropic has also confirmed that a regular user won't be able to see the watermark. According to the company, it has no practical impact on the quality or content of Claude's output, including creativity and readability. For those unaware, invisible watermarking and provenance systems are already being used for some AI-generated images, and text-based output will now follow a similar concept, although the underlying implementation is different. While the change is being introduced to comply with the EU AI Act, Anthropic says the watermark will initially be applied to Claude-generated text worldwide. "We’re applying watermarking globally at launch because we don't yet have a durable way to scope it by region," Anthropic explained in a blog post. Anthropic says future Claude models will generate watermarked text. Models launched before August 2, 2026, are covered by the EU's transition period, and Anthropic says it is working to add watermarking to those models over the coming months. Claude's watermark doesn't add hidden characters Anthropic says its implementation is based on Google DeepMind's SynthID-Text approach and explained that it works during generation, with certain exceptions. As you may be aware, AI models generate text by repeatedly choosing which token could reasonably come next. Instead of adding characters or modifying the finished response afterward, Claude's watermark changes the source of randomness used when making some of those choices. "Watermarking uses low-stakes choices like these—which occur many times over a piece of generated text—to leave a pattern in Claude’s responses. That pattern is undetectable to the reader, but is detectable to anyone who has a key that encodes it," Anthropic explained. "When watermarking is used, choices are still made at random, but the source of the randomness is different. Instead of using an arbitrary random number generator to pick the next word, watermaking uses the key and a few words that come before to settle what word the model should pick." "That is, the words that Claude picks are still random, but now, one can check the sequence of words and see if it’s consistent with the choices Claude would make if it was using the key. If it is, one can assign a probability that the text was generated by Claude." I also read the research paper on the topic, and here's an excerpt that explains how generative watermarking works: Generative watermarking works by carefully modifying the next-token sampling procedure to inject subtle, context-specific modifications into the generated text distribution. Such modifications introduce a statistical signature into the generated text; during the watermark detection phase, the signature can be measured to determine whether the text was indeed generated by the watermarked LLM. A key benefit of the approach is that the detection process does not require performing computationally expensive operations or even access to the underlying LLM (which is often proprietary). The paper goes in depth and has more examples, but the important part is that Anthropic is not adding a visible marker or hidden characters to Claude's response. Instead, when Claude has multiple reasonable choices for what to generate next, the watermarking system uses a secret key and some of the preceding words as part of the randomness used to make that choice. Those individual choices should look completely normal to a reader, but across a sufficiently long piece of text, they leave behind a statistical pattern. A detector that has Anthropic's key can examine the sequence of words and determine how consistent it is with the choices Claude would have made while using the watermark, allowing it to estimate the likelihood that Claude was involved in writing the text. According to Anthropic, internal testing found no impact on creativity, readability, or the content of Claude's responses. The company also says watermarking requires no additional tokens and has a negligible impact on generation speed. "Nothing is added to the text and there are no hidden characters," Anthropic noted. "Watermarking doesn’t require extra tokens, and will not be more expensive." Code and factual answers may carry less watermarking As I mentioned, there are certain exceptions to watermarking, and they're for good reasons. For factual statements where only one answer is correct, Anthropic says the watermark does not interfere with the choice. Likewise, the same principle applies to code, where replacing one term with another could break the output. "Where an exact output is required—where there isn’t a choice, and something would be factually wrong or a piece of code would break if a different term was chosen—the watermark isn’t applied." "For example, once the model has written “2 + 2 =”, there is a very clear best choice for the next token (if the model is completing the sum, there isn’t an answer that’s equally as good as “4”; if it’s talking about George Orwell’s Nineteen Eighty-Four, there isn’t an answer that’s equally as good as “5”)," the company noted. "The “nudge” of the watermark wouldn’t be applied here. For the same reason, code—which in very many cases has to be exact—has generally less watermarking than some other forms of text." Anthropic notes that watermarking can still be used in parts of code where arbitrary choices exist, such as comments, but says it should have a negligible effect on the actual code produced. This aligns with Google's SynthID-Text paper, which notes: There are two primary factors that affect the detection performance of the scoring function. The first is the length of the text x: longer texts contain more watermarking evidence, and so we have more statistical certainty when making a decision. The second is the amount of entropy in the LLM distribution when it generates the watermarked text x. For example, if the LLM distribution is very low entropy, meaning it almost always returns the exact same response to the given prompt, then Tournament sampling cannot choose tokens that score more highly under the g functions. In short, like other generative watermarks, Tournament sampling performs better when there is more entropy in the LLM distribution, and is less effective when there is less entropy. It is also worth noting that light proofreading of human-written text may leave too little Claude-generated material for reliable detection. Anthropic says the watermark only applies to words Claude actually chooses, so a few grammar or punctuation changes might not provide enough evidence. Anthropic says a translation produced by Claude carries a watermark because Claude chooses every word in the translated output. Anthropic is building an API to detect Claude watermarks It turns out that there'll be an easier way to detect the watermarks, as Anthropic plans to offer a watermark detection API. The API will be able to estimate the likelihood that Claude was involved in writing a piece of text, but Anthropic stresses that this is not the same as proving who wrote it. A Claude watermark also cannot identify whether the text was written by another AI model, since other providers may use different watermarking methods and different keys. "A watermark can only determine that Claude was likely involved with the content at some point. It cannot distinguish “Claude wrote this” from “Claude heavily edited this.” "Light editing probably won’t remove the watermark completely; a complete rewrite where every word is replaced will." Detection also becomes less reliable with small samples because there are fewer word choices for the detector to analyze. For generated PNG, JPG, and SVG files, Anthropic is taking a different approach. Claude will attach cryptographically signed C2PA provenance metadata indicating that the file was created or processed with Claude, rather than modifying the file itself with an embedded watermark. Overall prevention scores can hide what happens after initial access. Once attackers are using valid credentials, prevention drops sharply. The Blue Report 2026 measures defenses technique by technique across 338 million simulations run in customer production environments. Get the report
bleepingcomputer.comAug 14, 2026extracted
Detección de un acceso no autorizado a datos de clientes de Origin Energy
Detección de un acceso no autorizado a datos de clientes de Origin Energy 30/07/2026 Jue, 30/07/2026 - 13:25 Durante el mes de julio de 2026, Origin Energy detectó indicios de un posible incidente de ciberseguridad relacionado con el acceso no autorizado a información de clientes. La compañía indicó posteriormente que llevaba revisando una posible amenaza desde principios de julio, aunque la información disponible en ese momento no permitió considerarla creíble. El 22 de julio, tras recibir nuevos datos que apuntaban a que el incidente podía haberse materializado, la empresa activó su respuesta, inició una investigación formal y notificó a las autoridades competentes. La empresa confirmó que la información comprometida podía incluir nombres, direcciones, fechas de nacimiento, números de teléfono, información de las cuentas de cliente y los últimos dígitos de tarjetas bancarias o cuentas bancarias, precisando que esos datos parciales no permitían realizar pagos ni acceder a las cuentas financieras. Posteriormente, el 28 de julio, la compañía informó de que la fase inicial de su revisión estimaba que aproximadamente 900.000 clientes actuales y antiguos se habían visto afectados. Como respuesta, Origin comenzó a contactar directamente con las personas afectadas, habilitó líneas de atención específicas, ofreció servicios especializados de protección de identidad y apoyo en ciberseguridad, contrató expertos independientes en análisis forense y seguridad, reforzó la protección de sus sistemas y mantuvo la coordinación con el Australian Cyber Security Centre, la Australian Federal Police y la Office of the Australian Information Commissioner.&nbsp; En la actualidad, el incidente continúa bajo investigación y Origin Energy mantiene abierta su respuesta al suceso. Según la información oficial más reciente, la empresa ha completado la fase inicial de revisión para determinar el alcance de la exposición de datos y continúa notificando individualmente a las personas afectadas, al tiempo que mantiene disponibles los servicios de asistencia y protección ofrecidos tras el incidente. &nbsp; Referencias 22/07/2026 thenextweb.com Origin Energy investigates potential breach of customer data 23/07/2026 reuters.com Australia's Origin Energy confirms customer data breach (Reuters) 23/07/2026 originenergy.com.au Update on Data Security Incident 28/07/2026 originenergy.com.au Further Update on Data Security Incident 28/07/2026 reuters.com/ Australia's Origin Energy flags possible data exposure of about 900,000 customers (Reuters) 28/07/2026 abc.net.au Origin Energy believes 900,000 customers' data accessed in breach (ABC News) Etiquetas Ciberdelito Filtración de datos Sector energía
incibe.esJul 30, 2026extracted
Cadena de vulnerabilidades críticas en WordPress, wp2shell
Cadena de vulnerabilidades críticas en WordPress, wp2shell 28/07/2026 Mar, 28/07/2026 - 11:33 A mediados de julio de 2026 se hizo pública una cadena de vulnerabilidades críticas que afectaba al núcleo de WordPress, posteriormente denominada wp2shell. El incidente tuvo su origen en dos fallos presentes en WordPress Core que, al combinarse, permitían a un atacante remoto ejecutar código sin necesidad de autenticarse ni de explotar plugins o temas adicionales. El equipo de WordPress coordinó la divulgación de la incidencia con los investigadores que la notificaron de forma responsable a través de su programa de recompensas, publicando simultáneamente versiones de seguridad para corregir el problema. La publicación de las actualizaciones marcó el inicio de la respuesta oficial frente a un riesgo que afectaba a instalaciones vulnerables del gestor de contenidos. Tras la publicación de los parches, diversas empresas de ciberseguridad confirmaron la explotación activa de la cadena de vulnerabilidades contra sitios que aún no habían sido actualizados. Los ataques observados consistían en la instalación de webshells, la creación de usuarios con privilegios administrativos y el despliegue de complementos maliciosos para mantener la persistencia en los sistemas comprometidos. Las versiones afectadas correspondían a determinadas ramas de WordPress 6.8, 6.9 y 7.0, mientras que el proyecto publicó las versiones correctoras 6.8.6, 6.9.5 y 7.0.2. Como medida adicional, el equipo de WordPress activó las actualizaciones automáticas forzadas para las instalaciones compatibles y recomendó a los administradores actualizar inmediatamente sus sitios, así como comprobar si habían sufrido una intrusión antes de aplicar únicamente el parche. En la actualidad, el estado del incidente es el de una vulnerabilidad corregida, con actualizaciones de seguridad disponibles para todas las ramas afectadas y con campañas de explotación documentadas contra sistemas que permanecían sin actualizar. El proyecto WordPress mantiene como recomendación oficial la instalación de las versiones corregidas mediante el mecanismo de actualización automática o manual, mientras que distintos organismos y entidades de ciberseguridad continúan alertando de la existencia de intentos de explotación sobre instalaciones vulnerables. Hasta la fecha, la información oficial difundida por WordPress se centra en la disponibilidad de las correcciones y en la necesidad de mantener los sitios actualizados, sin comunicar cambios posteriores respecto al alcance del incidente ni anunciar nuevas medidas adicionales relacionadas con esta cadena de vulnerabilidades. &nbsp; Referencias 17/07/2026 wordpress.org WordPress 7.0.2 Release 18/07/2026 seguridadenwordpress.com wp2shell: la RCE de WordPress que afecta tu hosting 19/07/2026 cisoadvisor.com.br wp2shell: Un fallo crítico en el núcleo de WordPress permite la ejecución remota de código (RCE) 20/07/2026 securityweek.com WP2Shell WordPress Vulnerabilities Exploited in the Wild 22/07/2026 hispasec.com Una cadena crítica en WordPress facilita la instalación de webshells sin contraseña Etiquetas Actualización CMS Vulnerabilidad Wordpress
incibe.esJul 28, 2026extracted
ChatGPT joins the most impersonated brands in phishing attacks
ChatGPT joins the most impersonated brands in phishing attacks Microsoft continued to be the most impersonated brand in Q2 2026, accounting for 23% of all brand phishing attempts. LinkedIn, Google, Apple, and Amazon followed, with the five brands together making up more than half of all brand phishing attempts tracked during the quarter, according to Check Point’s Q2 2026 Brand Phishing Report. Fake ChatGPT Plus billing email (Source: Check Point) Technology remains the top target, but… Brand phishing exploits trusted brands people recognise and use every day. According to Check Point, technology remained the most impersonated sector, followed by social networks and banking. These industries handle users’ identities, finances, and professional relationships, making them valuable targets for attackers and the accounts people would be quickest to protect if they knew an attack was underway. ChatGPT entered the list of the 10 most impersonated brands for the first time, and Check Point says that we should expect AI platforms to keep climbing the list in future quarters. “As AI tools move from novelty to daily habit for millions of people managing subscriptions, payments, and work tasks through them, they become just as attractive a target as any bank or tech giant,” the company noted. Recognizing phishing Phishing campaigns documented this quarter targeted both consumers and organizations. Attackers impersonate familiar companies through email, fake websites, or both to steal login credentials, payment details, and personal information. But there are usually tell-tale signs that can help users identify phishing pages and emails: distorted logos, buttons and links that don’t work, domains that don’t match or are obviously not related to the impersonated brand, spelling errors. Some of these things can be spotted immediately, while finding others requires users to do a more thorough review. One of the things that should push users to engage in the latter are emails that trigger a sense of urgency. “Payment failures, security alerts, and required updates all push you to act before you stop to think, which is exactly the point,” Check Point said, and pointed out that as attackers increasingly use AI tools to create logos and webpages, “subtle distortions and inconsistencies are becoming reliable indicators that a site is fraudulent.”
helpnetsecurity.comJul 27, 2026extracted
ChatGPT Among Top 10 Most Impersonated Brands in Phishing Attacks, Says Check Point
Open AI’s ChatGPT entered the top 10 of the most impersonated brands in phishing attacks for the first time in the second quarter of 2026, according to a Check Point study. This included a fake "ChatGPT Plus payment failed" email the cybersecurity company observed in June. The malicious email was dressed up to look exactly like an OpenAI billing notice and led victims to a page built purely to steal full credit card details. The inclusion of OpenAI’s top customer-focused tool is “a strong signal of where attacker attention is heading next,” said Check Point. “As AI tools move from novelty to daily habit for millions of people managing subscriptions, payments, and work tasks through them, they become just as attractive a target as any bank or tech giant. Expect AI platforms to keep climbing this list in future quarters.” Big Tech Organizations: The Most Impersonated Brands As detailed in Check Point’s Q2 Brand Phishing Report, Microsoft remains the top impersonated brand, , as it did in the previous quarter. It accounts for 23% of all phishing attempts, nearly double the share of LinkedIn, the second-most targeted brand – also owned by Microsoft. Google, Apple and Amazon also made the top five most impersonated brands, which accounted for over half of all phishing attempts. Brand phishing is described by Check Point as an operation where a scammer impersonates a trusted, well-known company, through email, a fake website or both, in order to steal login credentials, payment details or personal information. Real world cases this quarter ranged from fake payment failure emails to full replica online stores, fake login pages and malware disguised as software updates. How to Prevent Brand Phishing As the top five most impersonated brands in Q2 2026 suggests, technology was the most targeted industry overall, followed by social networks and banking. Other real cases in the report included a cloned Michael Kors store that replicates the entire checkout, a fake UNIQLO storefront in a country where it doesn't even operate and a dodgy PayPal login page with a warped logo that looks AI-generated. In a blog published on July 23, Check Point provided recommendations to mitigate the threat of brand phishing. These include: Stopping phishing messages inline before they reach an inbox, rather than relying on detection once the damage is already done Using AI powered detection to catch brand impersonation, business email compromise, credential harvesting, QR code phishing and AI generated attacks with a level of accuracy manual review can’t match Consolidating email and workspace protection across Microsoft 365, Google Workspace and collaboration tools into a single platform, reducing operational complexity Automating investigation and response so security teams can resolve real threats faster Image credit: Celia Ong / CKA / Shutterstock.com
infosecurity-magazine.comJul 24, 2026extracted
Investigación sobre la filtración de datos personales de miembros de instituciones sensibles del Estado
Investigación sobre la filtración de datos personales de miembros de instituciones sensibles del Estado 23/07/2026 Jue, 23/07/2026 - 08:34 Durante los primeros meses de 2026, las autoridades españolas detectaron una campaña de difusión no autorizada de información confidencial que afectó a diversas instituciones consideradas sensibles para la seguridad del Estado. La investigación se inició tras comprobar que datos personales pertenecientes a miembros de organismos públicos estaban siendo publicados y compartidos en distintos canales de Internet, lo que suponía un riesgo para la privacidad de los afectados y para la seguridad institucional. A partir de ese momento, la Policía Nacional puso en marcha una investigación especializada para identificar el origen de las filtraciones, determinar el alcance de la información comprometida y esclarecer las circunstancias en las que se había producido el acceso y la posterior difusión de los datos. Como resultado de la investigación, la Policía Nacional detuvo a un menor de edad en la provincia de Granada como presunto responsable de un delito de revelación de secretos. Según la información oficial, los datos filtrados correspondían a miembros de organismos como la Fiscalía General del Estado, el Instituto Nacional de Ciberseguridad (INCIBE), el Consejo de Seguridad Nacional, la Policía Nacional, la Guardia Civil, el Ministerio de Hacienda y la Agencia Tributaria, entre otros. La actuación policial incluyó la práctica de un registro domiciliario en el que se incautó diverso material informático para su análisis pericial.&nbsp; En la actualidad, el caso continúa bajo investigación judicial y policial. De acuerdo con la información facilitada por el Ministerio del Interior, el detenido ha sido puesto a disposición de la autoridad judicial competente y las diligencias siguen abiertas para completar el análisis de las pruebas obtenidas durante el registro y esclarecer todos los extremos del incidente. Hasta la fecha, las autoridades no han informado públicamente de nuevos afectados, de la existencia de más personas investigadas ni de una ampliación del alcance de la filtración. &nbsp; Referencias 01/06/2026 www.europapress.es datos personales de miembros de instituciones sensibles del Estado 01/06/2026 www.infobae.com Detenido un menor de edad por la filtración masiva de datos personales de miembros de instituciones sensibles del Estado 01/06/2026 www.interior.gob.es La Policía Nacional detiene a una persona por la filtración masiva de datos personales de miembros de instituciones sensibles del Estado 01/06/2026 elpais.com Detenido un menor por la filtración masiva de datos confidenciales de altos cargos de la seguridad del Estado Etiquetas Ciberseguridad Filtración de datos
incibe.esJul 23, 2026extracted
Romania’s land registry hit by cyber attack, data allegedly for sale
Romania’s land registry hit by cyber attack, data allegedly for sale Romania’s National Agency for Cadastre and Land Registration (ANCPI) suffered a major disruption on Tuesday, July 14, when its e-Terra cadastre and land registry app became unavailable to users. What was first declared to be a “major technical incident” has now been confirmed as a cyber attack. While the circumstances are still being investigated by the competent state institutions, ANCPI stated that the data administered through its IT systems has not been compromised as a result of this incident. Property transactions caught in the outage “From the information we have at this time, we estimate that, most likely, the e-Terra application will not be available until the end of the current week,” the agency added in a Facebook post published on Wednesday, July 15. “We regret the situation created and assure you that our technical teams are making every effort to restore the functioning of the systems under safe conditions for all users, as soon as possible.” ANCPI promised to release updates as they continue the investigation, but in the meantime, the outage has stalled real estate transactions already in progress. Adrian Vascu, Senior Partner at Romanian business advisory firm Veridio, argued in a LinkedIn post that the disruption exposes a deeper problem: digitalized systems built without backup provisions for when they fail. “A failure can happen at any time, but it is mandatory to ensure continuity or an alternative,” he wrote. “Digitalization quickly creates dependency, but it must also ensure trust.” Threat actor claims data theft and ransomware deployment Dark Web Informer flagged that a threat actor who goes by “ByteToBreach” is trying to sell on a dark web forum data allegedly stolen from ANCPI. They claim to have compromised data of Romanian citizens and various ANCPI databases, made a copy of the agency’s GitLab servers and the source code contained within, and deployed ransomware. The threat actor provided as proof screenshots made during the intrusion. ByteToBreach is known for selling on DarkForums data stolen from a variety of organizations around the world. “Based on ByteToBreach posts, he uses a mix of multiple technical approaches: Exploiting known vulnerabilities in cloud and corporate infrastructure, reusing stolen credentials harvested from infostealers and phishing, and at times resorting to brute force or misconfiguration based access to gain footholds. Once inside, the focus is data exfiltration – employee records, databases, backups, and sensitive documents that are later sold or leaked publicly to prove claims,” says cyber threat intelligence company KELA Cyber. “Several incidents included datasets that were later corroborated by affected organizations or contained verifiable technical artifacts, underscoring that many of the actor’s claims were not mere bluff.” Given that track record, ByteToBreach’s claim may well be substantiated, but for now it remains unverified. UPDATE (July 20, 2026, 05:20 a.m. ET): “At present, ANCPI’s IT infrastructure is undergoing an extensive process of reinstallation and consolidation. The institution’s technical teams, together with cybersecurity specialists, are carrying out activities to restore, verify, and strengthen protective measures, so that services can be resumed under conditions of maximum security,” the agency stated over the weekend on its site’s homepage. ANCPI also said that the attacker did not succeed at wiping all of its backed up data, as it stores backups at several locations. “The resumption of the operation of IT applications and services will be carried out in stages, as each component is verified, secured, and validated from a cybersecurity standpoint, so that their operation takes place under conditions of maximum security and stability,” the agency added, and said that technical and criminal investigations into the attack are still ongoing. In related news, the Romanian Ministry of Investments and European Projects announced on July 16 that the Private Beneficiaries Procurement application, through which private beneficiaries of projects financed under European Union’s Cohesion Policy carry out procurement procedures, was the target of a cyber incident and is currently offline. Subscribe to our breaking news e-mail alert to never miss out on the latest breaches, vulnerabilities and cybersecurity threats. Subscribe here!
helpnetsecurity.comJul 16, 2026extracted
Incidente de ciberseguridad en una filial de Indra.
Incidente de ciberseguridad en una filial de Indra. 16/07/2026 Jue, 16/07/2026 - 10:36 A comienzos de julio de 2026, Indra confirmó que había sufrido un incidente de ciberseguridad que afectó a una de sus filiales. Según la información facilitada por la propia compañía, el suceso consistió en un ataque de tipo ransomware detectado por sus sistemas de seguridad, lo que motivó la activación inmediata de los protocolos internos de respuesta ante incidentes.&nbsp; Indra explicó que el incidente afectó únicamente a una de sus filiales y que no se produjo una propagación al resto de sociedades del grupo. La compañía señaló que su equipo de respuesta ante incidentes de seguridad (CSIRT) activó de forma inmediata las medidas de contención y análisis previstas para este tipo de situaciones. Asimismo, informó de que la prestación de sus servicios continuó desarrollándose con normalidad y que la seguridad de las operaciones no se vio comprometida. Paralelamente, la empresa puso en marcha una investigación para esclarecer las circunstancias del ataque y reforzó las medidas de ciberseguridad con el objetivo de prevenir posibles incidentes similares. La empresa ha confirmado que continuaba investigando el origen y el alcance del incidente como parte de sus procedimientos internos de respuesta. Hasta el momento de su última comunicación pública, Indra sigue sosteniendo que el impacto del ciberataque es mínimo, que la actividad de la compañía se desarrollaba con normalidad y que no existen cambios en la valoración oficial del estado del incidente. &nbsp; Referencias 01/07/2026 cincodias.elpais.com Indra sufre un ciberataque pero “garantiza la seguridad y la continuidad de sus servicios” 01/07/2026 www.europapress.es Indra "garantiza la seguridad y la continuidad de sus servicios" tras sufrir un ciberataque 01/07/2026 www.servimedia.es Indra registra un ciberataque en una de sus filiales Etiquetas Ciberseguridad Filtración de datos Ransomware
incibe.esJul 16, 2026extracted
US: Pentagon Suspends CMMC Phase II Requirements for Defense Contractors
The US Department of Defense (DoD) has suspended the Cybersecurity Maturity Model Certification (CMMC) Phase II requirements until it reviews the program to allow for more innovation in the US defense industrial base (DIB). Originally scheduled to come into effect on November 10, 2026, the requirements corresponded to the second stage of the DoD’s phased rollout for the CMMC, a program designed to enhance cyber hygiene for US defense contractors and subcontractors handling federal contract information (FCI) and controlled unclassified information (CUI) for the DoD – also known as the Department of War (DoW). While the first phase (CMMC Phase I) allowed companies to self-report their cybersecurity compliance levels, this second phase would have required contractors that work with the military and handle sensitive information to have this checked by an outside company. Specifically, CMMC Phase II requirements were designed to transition US defense contractors handling CUI from basic self-attestations to mandatory, independent assessments led by Certified Third-Party Assessment Organizations (C3PAOs) to verify compliance with the 110 security controls referred to in NIST SP 800-171, a standard published by the US National Institute of Standards and Technology (NIST). The DoD previously estimated that between 220,000 and 300,000 companies participate in the DIB, with roughly 80,000 that were expected to require CMMC Phase II. A CyberSheath report published in October 2025 revealed that only 1% of defense contractors felt fully prepared for CMMC Phase II audits. Furthermore, Phase II was supposed to be followed by a third and a fourth phase, scheduled to be completed in November 2027 and November 2028, respectively. Phase III was to introduce level 3 audits, led directly by the DoD, for contracts with the most sensitive data, while Phase IV would have meant all DoD contractors and subcontractors would need full CMMC compliance. CMMC Has Created “Bureaucratic Burdens” for the DIB To justify the suspension of CMMC Phase II, the DoD argued in its July 13 statement that the program has “created prohibitive compliance costs and bureaucratic burdens” instead of enhancing cybersecurity for DIB firms. “Recent data, including reports from the Small Business Administration (SBA), confirmed that CMMC compliance is forcing innovative companies out of the DIB which will delay the delivery of critical capabilities to the warfighters,” said the Department. Therefore, the DoD will establish a ‘CMMC Reform Task Force’ to conduct a 60-day, top-to-bottom review of the program to ensure that it is aligned with the Secretary of War Pete Hegseth's acquisition transformation system (ATS) strategy. This includes directives lowering barriers for small, medium and non-traditional businesses and “replacing bureaucratic compliance with scalable, resilient cybersecurity measures.” "Robust cybersecurity and operational resilience remain critical to protecting American innovation and supporting warfighter readiness. We believe the DIB can achieve both, while we reduce unnecessary government red tape,” said the Department’s CIO, A. Davies, who will be responsible for putting together the task force. During the interim period, the DoD said it will enforce cybersecurity compliance with the NIST SP 800-171 Rev 2 standard through self-assessments and select government-led assessments, “focusing on tangible cyber hygiene rather than administrative overhead.” Experts Warn Against Abandoning CMMC Compliance Efforts Following the announcement, some security compliance experts shared their interpretation for the sudden suspension. Dave Schroeder, director of National Security Initiatives at the University of Wisconsin Madison, said on LinkedIn that because CMMC is a program to prove a firm’s compliance with NIST 800-171 and DFARS 252.204-7012, the reason behind the recent DoD is likely due to not enough contractors being ready to comply with CMMC Phase II by Nov 10. Nelina Varenas, director and a founding member of the KDM Consortium, emphasized in a LinkedIn article published on July 14 that contractors should not interpret the delay as an opportunity to abandon their compliance efforts. "First, as the DoD announcement stated, all CMMC Level 1 self-assessment requirements remain in place," Varenas noted. She urged concerned organizations not to abandon their compliance efforts, warning that the delay should not be misinterpreted as a relaxation of standards. Instead, she advised the suspension should be viewed as valuable breathing room to ensure cybersecurity practices are implemented correctly and thoroughly before potential future enforcement resumes. The future of CMMC remains uncertain, but Varenas cautioned, "This is not the time to step back; it’s the time to ensure compliance is done right."
infosecurity-magazine.comJul 14, 2026extracted
Incidente de ciberseguridad con acceso no autorizado a datos de clientes de ElParking
Incidente de ciberseguridad con acceso no autorizado a datos de clientes de ElParking 14/07/2026 Mar, 14/07/2026 - 11:54 El incidente de ciberseguridad tuvo lugar el 14 de junio de 2026, fecha en la que ElParking, servicio integrado en el Grupo Mutua Madrileña, detectaron un acceso no autorizado a determinados datos personales de sus clientes. Según la información comunicada por la compañía, sus sistemas de seguridad identificaron la intrusión durante ese mismo día y activaron de forma inmediata los protocolos de respuesta para contener el incidente. El suceso afectó a la infraestructura que presta servicio a la aplicación ElParking, utilizada para la gestión de estacionamientos y otros servicios de movilidad. Desde el primer momento, la empresa informó de que el objetivo principal fue limitar el alcance del acceso no autorizado y preservar la continuidad de sus servicios mientras se analizaba el incidente. Como consecuencia del acceso no autorizado, quedaron expuestos determinados datos básicos de identificación y contacto de los usuarios, entre ellos el nombre, la dirección de correo electrónico, el número de teléfono, la matrícula del vehículo y el DNI cuando estos habían sido facilitados por los clientes. La compañía indicó que, tras las verificaciones realizadas, las contraseñas de acceso a la aplicación y los datos relativos a los medios de pago no se vieron comprometidos. Asimismo, comunicó que el acceso fue contenido y bloqueado de forma inmediata, reforzó la monitorización de sus sistemas y notificó el incidente a las autoridades competentes, incluida la Agencia Española de Protección de Datos, conforme a la normativa vigente. Además, recomendó a los clientes permanecer atentos ante posibles comunicaciones sospechosas o intentos de fraude que pudieran utilizar la información expuesta. En el momento de las últimas comunicaciones oficiales, la compañía manifestó que no tenía constancia de un uso indebido de los datos personales afectados y que la aplicación continuaba prestando servicio con total normalidad. MutuaMás y ElParking señalaron que el incidente permanecía bajo seguimiento mediante el refuerzo de las medidas de vigilancia y seguridad implantadas tras su detección. La empresa mantuvo abiertas las vías de atención para resolver las dudas de los clientes y reiteró su compromiso de informar sobre cualquier novedad relevante relacionada con el incidente. &nbsp; Referencias 16/06/2026 informacion.grupomutua.es Comunicado de la Mutua Madrileña 23/06/2026 escudodigital.com Mutua Madrileña comunica a sus clientes una brecha de datos en su app de parking nueve días después de conocer el incidente 23/06/2026 adslzone.net Filtración masiva de datos en MutuaMás: la compañía avisa de urgencia tras sufrir un preocupante hackeo 24/06/2026 abc.es 'ElParking', la app de MutuaMás, sufre una brecha de datos de sus clientes 24/06/2026 bandaancha.eu Filtración de datos de la app MutuaMás de Mutua Madrileña Etiquetas Cibercrimen Ciberdelito Ciberseguridad Filtración de datos
incibe.esJul 14, 2026extracted
CISA Details Incident Response to Exposed AWS GovCloud Keys
The US Cybersecurity and Infrastructure Security Agency (CISA) has detailed its response to internal CISA Amazon AWS GovCloud Keys and other information being made available in a public repository. The reaction came after KrebsOnSecurity detailed in May how a security researcher with GitGuardian had identified a public GitHub repository that exposed credentials to several highly privileged AWS GovCloud accounts and a large number of internal CISA systems. The GitHub repository was not part of CISA’s official GitHub but rather was a personal repository owned by a contractor. In an update published on June 9, CISA said, “Within moments of receiving this information, CISA’s Office of the Chief Information Officer (OCIO) took swift and comprehensive action to mitigate any exposure to CISA’s cloud resources and code repositories.” CISA’s internal incident response began on May 15. The actions taken by the agency’s incidents responders included efforts to eliminate public exposure, prevent further harm, understand the scope of information shared, assess the impact and implement corrective actions. It was highlighted that no customer or mission data was exposed and leaked credentials were not used outside of CISA’s environments. The third-party individual uploaded copies of a CISA build and deployment repository to their personal GitHub account for the purpose of creating cloud infrastructure autonomously. This repository included CISA’s Infrastructure As Code and build code. Take Security Tips Seriously In its reflections on the incident the cybersecurity agency said it was vital to take cybersecurity tips and external reporting seriously. CISA thanked the security researcher and the reporter for their collaboration. CISA also said the incident highlighted the need to adopt zero trust principles in order to protect systems and development environments. It was also highlighted that strong logging capabilities are vital. CISA said its SOC has the necessary logs to successfully investigate the incident and continuous improvement of logging capabilities remains a key element of a strong security program. CISA said the incident drew attention to several areas for improvement, including tighter controls over public code repository access, stronger monitoring for exposed secrets, and the development of comprehensive GitHub and cloud incident-response playbooks. The agency also plans to simplify security researcher reporting channels. In this instance, these channels “were not well defined” which resulted in the security researcher attempting to communicate via multiple channels. These included emailing the contractor, submitting through CISA’s vulnerability disclosure platform (which is intended for vulnerabilities impacting the broader cybersecurity community), and ultimately involving a reporter. Finally, CISA plans to strengthen security guardrails in developer environments and improve cryptographic key management to enable faster credential rotation during future incidents. “It is not a matter of “if”, but “when” a cybersecurity incident will happen to your organization. It is important to the broader cybersecurity community that we address these matters openly to strengthen trust and foster transparency. Such transparency unlocks opportunities for learning that will enhance not only CISA’s security posture but that of other organizations as well,” CISA wrote. CISA also published the update on its LinkedIn channel with one commenter praising the agency for its willingness to document both the strengths and the gaps in its response to the indent.
infosecurity-magazine.comJul 10, 2026extracted
Investigación de una posible filtración de datos relacionados con Hogami de Leroy Merlin
Investigación de una posible filtración de datos relacionados con Hogami de Leroy Merlin 09/07/2026 Jue, 09/07/2026 - 09:36 A finales de junio de 2026, Leroy Merlin España comunicó que estaba investigando un incidente de seguridad relacionado con Hogami, su plataforma de servicios de instalación, mantenimiento y reforma. La información disponible sitúa el suceso en torno al 30 de junio de 2026, momento en el que la compañía activó sus procedimientos internos tras detectar la posible exposición de datos de clientes. El caso se enmarca en un incidente de ciberseguridad reciente cuya existencia fue reconocida por la empresa en el contexto de sus actuaciones de contención y análisis. Según la información difundida, la posible filtración habría afectado a determinados registros de clientes vinculados a Hogami, incluyendo datos identificativos y de contacto como nombre y apellidos, correo electrónico, número de teléfono, DNI y dirección postal, además de algunos identificadores técnicos. La empresa indicó que no se vieron comprometidas contraseñas, credenciales de acceso ni datos bancarios o de pago. Tras detectar el incidente, Leroy Merlin España puso en marcha sus protocolos de seguridad y protección de datos, aplicó medidas de contención, refuerzo y monitorización, informó a las personas afectadas a través de sus canales oficiales y trasladó el caso a las autoridades competentes. Actualmente, la situación sigue descrita públicamente como una investigación en curso sobre una posible filtración de datos. La posición comunicada por la empresa se centra en que el incidente ha sido identificado, que ya se han activado medidas de respuesta y que la notificación a afectados y autoridades ya se ha realizado.&nbsp; &nbsp; Referencias 25/06/2026 darkwebinformer.com Leroy Merlin Spain Customer Database of Nearly 55,000 Records Allegedly Leaked 26/06/2026 www.hendryadrian.com Leroy Merlin Spain Customer Database of Nearly 55,000 Records Allegedly Leaked 30/06/2026 ciberseguretat.gencat.cat Un incidente de seguridad en la plataforma Hogami, de Leroy Merlin, expone información personal de los clientes Etiquetas Ciberdelito Ciberseguridad Comercio Filtración de datos
incibe.esJul 9, 2026extracted
3 Ways AI Powers Service Desk Attacks and How to Prevent Them
IBM’s 2025 Cost of a Data Breach Report found that 16% of breaches studied involved attackers using AI tools, most often for phishing or deepfake impersonation attacks. For security teams, that has direct implications for the service desk. The service desk is a natural target for social engineering, as an attacker that convinces an agent they are a legitimate user may not need to bypass technical controls. They can simply ask for help getting around them. AI makes that easier, helping attackers sound more credible by personalizing their approach. Onboarding is particularly exposed in a threat landscape where AI enables more convincing social engineering attacks. New employees need fast access, but the organization may not yet have strong familiarity with who they are. Attackers can exploit that gap, so service desk agents need better ways to prove identity before they hand over credentials, reset MFA or approve sensitive changes. Three ways AI aids service desk attacks 1. AI makes impersonation more convincing High-profile attacks against M&S, MGM Resorts, Clorox and others all started with a simple question to the service desk: “Can you help me get access?”. From there, the threat actors gained access to accounts, escalated their attacks and cost the victim organizations millions. Impersonation has long been a risk at the service desk, and AI makes it even harder for agents to judge whether a request is genuine. Attackers can now use generative AI to create polished emails, convincing chat messages and realistic call scripts in seconds. In more targeted attacks, they can also use AI-generated voice or video to impersonate an employee. Onboarding is especially exposed. New employees are not always known to IT teams, and first-day access issues are expected. An attacker posing as a new hire can use AI to sound credible, reference the right department and create just enough urgency to push a request through. 2. AI accelerates reconnaissance and personalization More personal information is available on the internet than ever before, and AI helps threat actors find it. When defending against onboarding attacks, this is a real concern. Organizations often share more than they realize. A welcome post might name a new employee, or a job advert might mention the systems the company uses. A LinkedIn profile might show the hiring manager, team structure and office location. Threat actors can pull this information, then use AI to scrape more from LinkedIn, company websites, job posts, press releases and social media. They can then turn those details into a believable story. Names, roles, locations, departments, internal tools and reporting lines can all be worked into a script that sounds credible. That level of detail can make a malicious request look routine. And when a request feels routine, it is more likely to move quickly. 3. AI helps attackers scale service desk attacks An attacker no longer needs to create a social engineering campaign from scratch. They can use AI to create dozens of phishing email variations, test different pretexts and adapt their wording to tailor their efforts. That creates a problem for service desks because they are built to respond quickly. Attackers know this, so use urgency and persistence to make a malicious request feel like another routine task in a busy queue. AI makes it easier for attackers to adjust their approach, and they can try the same basic request across multiple channels or agents until someone approves the reset, releases the credential or changes the recovery method. Verizon’s Data Breach Investigation Report found stolen credentials are involved in 44.7% of breaches. Effortlessly secure Active Directory with compliant password policies, blocking 6+ billion compromised passwords, boosting security, and slashing support hassles! Try it for free How to prevent AI-enabled service desk attacks AI-enabled attacks are designed to look normal, so prevention cannot rely on service desk agents making perfect judgment calls under pressure. It’s here that specialized solutions can help secure an especially high risk process the service desk deals with: onboarding. Specops Secure Onboarding helps secure onboarding end-to-end and beyond, ensuring agents have the tools they need to confidently verify identity and protect new credentials from interception. 1. Secure password delivery during onboarding A new starter needs credentials quickly, but sending a password via SMS or email creates risk if it’s intercepted. A safer approach is to not send credentials at all. Specops Secure Onboarding instead allows the IT team to send secure enrollment links to new hires, with instructions explaining how to create their own strong passwords. As there’s no credential created or shared from the service desk, this eliminates the risk of interception. 2. Use biometric liveness detection to defeat impersonation Traditional identity checks are becoming less reliable; for instance, the answers to security questions can often be guessed from information an attacker can source from social media profiles. Especially in instances where the service desk may not be familiar with the employee, such as a new starter on their first day, agents need confidence that the person requesting access isn’t an attacker impersonating a genuine employee. Biometric liveness detection, delivered through solutions like Specops Secure Onboarding, can help by confirming that a real person is present during verification, rather than a static image, recording, mask or deepfake. This is especially useful for remote onboarding, where the service desk may never meet the employee face to face. 3. Verify identity before sensitive service desk actions Sensitive actions need stronger identity verification before they are approved. For instance, a request to reset the password of a privileged account should trigger checks as biometric liveness detection to provide high assurance that the request is genuine and the person making it linked to the correct account. Specops Secure Onboarding ensures that verification takes place before agents complete actions like password resets. Agents can enforce verification through strong identity checks and make trust decisions with greater confidence. Protect your service desk from AI-enabled attacks with Specops Specops Secure Onboarding helps organizations secure the service desk during high-risk actions by placing identity verification at the center of processes like onboarding, delivering: Stronger protection against identity-based attacks: Replace assumed trust with verified identity throughout onboarding, helping service desk teams defend against AI-powered impersonation. A consistent onboarding experience: Give every new starter the same secure process, wherever they are based, without adding unnecessary friction for HR teams or employees. Less risk at the service desk: Verify identity before sensitive actions are taken, so agents are not left to judge whether a request is genuine based on trust alone. If you’re interested in seeing how Specops Secure Onboarding can help your service desk defend against sophisticated social engineering attacks, contact us today or book a demo. Sponsored and written by Specops Software.
bleepingcomputer.comJul 8, 2026extracted
Vulnerabilidad en iPhone con procesadores A12 y A13
Vulnerabilidad en iPhone con procesadores A12 y A13 07/07/2026 Mar, 07/07/2026 - 10:45 En junio de 2026 se hizo público un hallazgo de ciberseguridad que afecta a determinados modelos de iPhone equipados con los procesadores A12 y A13. El suceso se produjo cuando los investigadores de la empresa Paradigm Shift identificaron y divulgaron una vulnerabilidad localizada en el BootROM o SecureROM de estos chips, un componente que forma parte de la cadena de arranque del dispositivo. Antes de la publicación de los detalles técnicos, los investigadores notificaron el descubrimiento al equipo de seguridad de Apple siguiendo el procedimiento habitual de divulgación responsable. La vulnerabilidad fue presentada como un fallo de hardware , es decir, una característica inherente al diseño del chip y no un problema introducido por una versión concreta del sistema operativo. Debido a esta naturaleza, el incidente se enmarca en una vulnerabilidad de bajo nivel cuya existencia se confirmó tras la publicación del informe técnico por parte de los investigadores. La investigación describe un exploit denominado usbliter8, que permite aprovechar la vulnerabilidad para comprometer la cadena de arranque de los dispositivos afectados bajo determinadas condiciones. Según el informe técnico, el ataque requiere disponer de acceso físico al iPhone, conectarlo mediante USB y ponerlo en modo DFU, por lo que no puede explotarse de forma remota a través de Internet. Los dispositivos afectados corresponden a modelos con procesadores A12 y A13, mientras que las generaciones posteriores incorporan un diseño de hardware diferente que no presenta este problema concreto. Al tratarse de un fallo residente en el BootROM, Apple no ha anunciado una actualización de software para corregirlo, ya que este tipo de componente no puede modificarse mediante una actualización de iOS. La compañía ya había introducido cambios de hardware en generaciones posteriores de sus procesadores para evitar esta vulnerabilidad. En la actualidad, el estado actual del suceso es el de una vulnerabilidad conocida, documentada y divulgada públicamente, cuya existencia ha sido reconocida mediante la notificación previa al fabricante y cuya mitigación se basa en las mejoras de hardware implementadas en las generaciones más recientes de dispositivos. &nbsp; Referencias 23/06/2026 www.europapress.es Algunos iPhone tienen una vulnerabilidad que no puede corregirse y que da pie a su hackeo 23/06/2026 www.abc.es Detectan una vulnerabilidad irreparable en los iPhone que permite su hackeo 23/06/2026 www.menorca.info Algunos iPhone tienen una vulnerabilidad que no puede corregirse y que da pie a su hackeo Etiquetas Ciberdelito Ciberseguridad Filtración de datos Hardware + Vulnerabilidad -
incibe.esJul 7, 2026extracted
Operación Endgame interrumpe las redes de malware de Amadey, StealC y SocGholish
Operación Endgame interrumpe las redes de malware de Amadey, StealC y SocGholish 02/07/2026 Jue, 02/07/2026 - 13:03 A finales de junio de 2026 se anunció una nueva fase de la Operación Endgame, una iniciativa internacional dirigida a desmantelar infraestructuras utilizadas por grupos de ciberdelincuencia para distribuir malware. La actuación se centró en las redes asociadas a las familias de malware Amadey, StealC y SocGholish, ampliamente empleadas para el robo de credenciales, la distribución de otras amenazas y el acceso inicial a sistemas comprometidos. La operación fue coordinada por Europol junto con autoridades policiales y judiciales de varios países, entre ellos Alemania, Países Bajos, Dinamarca, Reino Unido, Estados Unidos y Canadá, con la colaboración de diversas empresas del sector de la ciberseguridad. El objetivo principal fue interrumpir la infraestructura técnica que permitía el funcionamiento y la propagación de estas campañas maliciosas. Durante la operación, las autoridades ejecutaron acciones coordinadas para desmantelar la infraestructura empleada por los operadores de Amadey y StealC, lo que incluyó la intervención de cientos de servidores y dominios utilizados como centros de mando y control. Según la información facilitada por Europol, también se recuperaron aproximadamente 27 millones de credenciales robadas y se inmovilizaron activos en criptomonedas vinculados a la actividad delictiva. Los principales afectados por estas campañas fueron usuarios y organizaciones cuyas credenciales o sistemas habían sido comprometidos por el malware, así como las infraestructuras criminales utilizadas por los responsables de su operación. Las fuerzas de seguridad internacionales, en colaboración con empresas especializadas en ciberseguridad, coordinaron la identificación, incautación y desactivación de los recursos empleados para mantener activas estas amenazas. Según los datos de Europol y el resto de cuerpos policiales implicados, el golpe a las infraestructuras de Amadey, StealC y SocGholish interviniendo sus servidores y dominios ha frenado de forma temporal la actividad de estas redes de malware. Más allá de este bloqueo, la operación logró recuperar un volumen importante de credenciales robadas y congelar fondos vinculados a las actividades ilícitas. A pesar del éxito de estas primeras acciones dentro de la Operación Endgame, las autoridades dejaron claro en sus comunicados que el despliegue internacional contra el cibercrimen sigue en marcha; la investigación continúa totalmente abierta y la cooperación entre países se mantendrá activa para localizar nuevos servidores e identificar a los responsables. Entre los afectados figuran casi 9.000 equipos comprometidos localizados en España, de los que se obtuvieron más de 535.000 credenciales, así como 70.000 credenciales de los usuarios de 3.000 páginas webs españolas.&nbsp; INCIBE-CERT, en su labor como CERT Nacional de España para las entidades privadas, colabora activamente notificando estos casos dentro de su ámbito para que los afectados puedan desinfectar sus equipos y cambiar todas sus credenciales. &nbsp; Referencias 19/06/2026 thehackernews.com Operation Endgame Disrupts SocGholish Servers, Cleans 14,971 WordPress Sites 24/06/2026 www.operation-endgame.com Global cyber strike disrupts SocGholish, Amadey, and StealC malware networks 24/06/2026 www.europol.europa.eu Global cyber strike disrupts SocGholish, Amadey, and StealC malware networks 24/06/2026 arstechnica.com One-two punch delivered in global operation disrupts cybercrime “assembly line” 24/06/2026 www.microsoft.com StealC and Amadey: Breaking down infostealers and the cybercrime services that deliver them 24/06/2026 therecord.media Three ‘cybercrime as a service’ operations undercut by Microsoft, law enforcement 24/06/2026 www.theregister.com Microsoft uses AI to link two malware operations in racketeering suit 24/06/2026 cyberscoop.com In a first, a court takedown goes after two cybercrime tools at once 24/06/2026 www.bleepingcomputer.com Amadey, StealC malware operations disrupted in Operation Endgame action Etiquetas Cibercrimen Ciberdelito Ciberseguridad Contraseña + Malware -
incibe.esJul 2, 2026extracted
Evaluación de vulnerabilidades en sistemas clasificados de Estados Unidos mediante inteligencia artificial
Evaluación de vulnerabilidades en sistemas clasificados de Estados Unidos mediante inteligencia artificial 30/06/2026 Mar, 30/06/2026 - 13:20 Durante la segunda quincena de junio de 2026, en el marco de un ejercicio autorizado de evaluación de ciberseguridad llevado a cabo por organismos del Gobierno de Estados Unidos, trascendió que el modelo de inteligencia artificial Mythos fue utilizado para analizar la seguridad de sistemas clasificados. El ejercicio tenía como finalidad identificar vulnerabilidades de forma controlada y medir la capacidad de una IA avanzada para apoyar tareas de auditoría de seguridad. Mythos habría localizado vulnerabilidades en sistemas clasificados durante un ejercicio de red teaming autorizado, realizando esta tarea en un plazo de pocas horas. El objetivo del ejercicio era evaluar la eficacia de herramientas de inteligencia artificial para detectar debilidades de seguridad antes de que pudieran ser explotadas por actores maliciosos. No existen evidencias públicas de que los sistemas clasificados fueran comprometidos ni de que se produjera una filtración de información sensible como consecuencia de estas pruebas. Tampoco consta que la NSA informara de una brecha de seguridad derivada del ejercicio.&nbsp; La información disponible mantiene que las pruebas se desarrollaron en un entorno autorizado con fines de evaluación de capacidades y detección de vulnerabilidades. En consecuencia, no se ha informado oficialmente de sistemas afectados por un ataque, de datos comprometidos ni de una investigación sobre una brecha de seguridad, permaneciendo el episodio descrito públicamente como una actividad de evaluación y fortalecimiento de la seguridad. &nbsp; Referencias 21/06/2026 ecosistemastartup.com NSA: IA Mythos vulneró sistemas clasificados en horas 24/06/2026 es.euronews.com Una IA de Anthropic detecta vulnerabilidades en sistemas clasificados de EE.UU. en cuestión de horas Etiquetas Ciberdelito Inteligencia artificial Vulnerabilidad
incibe.esJun 30, 2026extracted
Detección y corrección de la vulnerabilidad CVE-2026-8713 en el complemento Avada Builder para WordPress
Detección y corrección de la vulnerabilidad CVE-2026-8713 en el complemento Avada Builder para WordPress 25/06/2026 Jue, 25/06/2026 - 12:02 A mediados de mayo, se identificó y procesó una vulnerabilidad crítica que comprometía la integridad de la infraestructura de los sitios web que utilizaban una herramienta de diseño específica dentro de la plataforma de gestión de contenidos WordPress. El comunicado oficial del suceso fue publicado a través del boletín de seguridad de la firma Wordfence el 18 de junio de 2026 detallando los pormenores del hallazgo una vez mitigado el riesgo inicial. El incidente consistió en el descubrimiento de una vulnerabilidad de severidad crítica, catalogada como CVE-2026-8713 con una puntuación CVSS de 9.1, que afectaba al complemento Avada (Fusion) Builder en todas sus versiones hasta la 3.15.3, impactando potencialmente a más de un millón de instalaciones activas en todo el mundo. El fallo radicaba en una validación insuficiente de las rutas de archivos en la función interna encargada de la limpieza periódica de las entradas de formularios almacenadas en la base de datos, lo que permitía a atacantes no autenticados realizar la eliminación de archivos arbitrarios mediante técnicas de salto de directorio (path traversal). Al enviar parámetros manipulados a través de un formulario público, un atacante podía borrar archivos esenciales del servidor como "wp-config.php", forzando a WordPress a entrar en su estado de instalación inicial y permitiendo a un tercero tomar el control administrativo del sitio. Ante este escenario, la empresa desarrolladora reaccionó implementando y distribuyendo con rapidez la versión 3.15.4 del complemento para solventar por completo este fallo de seguridad. Actualmente, la empresa de seguridad Wordfence ha confirmado que las reglas de su cortafuegos web están configuradas de forma activa para detectar y bloquear cualquier intento de explotación que intente utilizar el salto de directorio en los datos de los formularios de Avada. Las recomendaciones oficiales emitidas por los desarrolladores indican de manera taxativa que los administradores de sistemas que utilicen este complemento deben aplicar de forma inmediata la actualización a la versión 3.15.4 para mitigar cualquier vector de riesgo persistente en sus entornos de producción.&nbsp; &nbsp; Referencias 18/06/2026 wordfence.com Critical Unauthenticated Arbitrary File Deletion Vulnerability Patched in Avada Builder WordPress Plugin 19/06/2026 gbhackers.com Critical WordPress Plugin Bug Could Allow File Deletion Attacks on 1 Million Sites 12/05/2026 wpscan.com Avada Builder &lt; 3.15.2 - Unauthenticated SQL Injection via 'product_order' Parameter Etiquetas CMS Vulnerabilidad Wordpress
incibe.esJun 25, 2026extracted
Exposición de credenciales en dispositivos Fortinet asociada a la explotación de SSL-VPN
Exposición de credenciales en dispositivos Fortinet asociada a la explotación de SSL-VPN 22/06/2026 Lun, 22/06/2026 - 12:53 Recientemente, se ha publicado la existencia de un extenso listado de credenciales vinculado a dispositivos Fortinet, especialmente en FortiGate y entornos SSL-VPN expuestos a Internet. A esta secuencia de sucesos se le ha denominado FortiBleed. FortiBleed se podría vincular, en su origen, a la explotación de vulnerabilidades, como CVE-2023-27997 en FortiOS y FortiProxy SSL-VPN, corregida por Fortinet en junio de 2023. Esta vulnerabilidad afectaba al componente SSL-VPN y podía permitir la ejecución remota de comandos. En junio de 2026 se ha descrito la circulación de un conjunto de credenciales asociadas a decenas de miles de dispositivos Fortinet accesibles desde Internet, incluidos portales VPN y firewalls utilizados por organizaciones de múltiples sectores. Los afectados mencionados en esas coberturas son empresas y entidades cuyas credenciales habrían quedado expuestas, aunque la información observada parecía proceder de incidentes antiguos y de campañas de fuerza bruta, y no de una nueva vulnerabilidad. Las informaciones apuntan a usuarios y organizaciones que mantenían expuestos a Internet dispositivos Fortinet con SSL-VPN que en un momento dado eran vulnerables o tenían credenciales débiles, lo que habría permitido accesos no autorizados, el robo de configuraciones, credenciales y la posterior circulación de credenciales asociadas a esos equipos, así como la instalación de puertas traseras. Si no se aplicaron las actualizaciones a los sistemas publicadas por Fortinet, rotando después contraseñas, revisando los registros de acceso y reforzando la autenticación con mecanismos multifactor, pueden seguir siendo vulnerables a través de las credenciales obtenidas en su momento. Cabe destacar que el robo de credenciales se produjo en distintos momentos, y no todas las credenciales disponibles en el listado son válidas en el momento actual (por ejemplo, porque se haya cambiado después del robo de la misma), aunque desgraciadamente la mayoría de ellas parecen estar activas. No obstante, hay que recordar que no es suficiente con cambiar las credenciales del listado, dado que también es crucial asegurar tanto que el firmware se encuentre actualizado como la inexistencia de puertas traseras. Por otro lado, existe la posibilidad de que se comprometieran asimismo credenciales de usuarios que utilizaran el dispositivo en el período de compromiso. Tanto de los propios dispositivos como del tráfico enrutado a través de los mismos, ya que los actores instalaban sistemas para el análisis de tráfico obteniendo en múltiples protocolos contraseñas y hashes para romper por fuerza bruta mediante el uso de GPU. También se han documentado casos de posteriores movimientos laterales a sistemas internos. Las principales recomendaciones para las organizaciones listadas serían: Cambiar todas las credenciales administrativas y de VPN de FortiGate. Forzar autenticación multifactor en todas las interfaces de acceso remoto. Asegurarse que las inferfaces de gestión no se encuentren expuestas en Internet. Revisar los registros de gateway y autenticación en busca de actividad sospechosa. &nbsp; Referencias 12/06/2023 fortinet.com Analysis of CVE-2023-27997 and Clarifications on Volt Typhoon Campaign 12/06/2023 fortiguard.com Heap buffer overflow in sslvpn pre-authentication 13/06/2023 watchtowr.com Xortigate, or CVE-2023-27997 - The Rumoured RCE That Was 09/02/2024 incibe.es [Actualización 14/04/2025] Múltiples vulnerabilidades en FortiOS de Fortinet 17/06/2026 techcrunch.com Cybercriminals allegedly hacked tens of thousands of Fortinet firewalls used by major companies all over the world 18/06/2026 bleepingcomputer.com FortiBleed leak exposes Fortinet VPN credentials for 73,000 devices. 18/06/2026 itpro.com Passwords nicked for nearly 74,000 Fortinet devices 21/06/2026 socradar.io Dismantling FortiBleed 21/06/2026 socradar.io SOCRadar FortiBleed: Fortinet Firewalls Compromised
incibe.esJun 22, 2026extracted
UK Information Commissioner Resigns After Workplace Investigation
The UK’s information commissioner, John Edwards, has resigned following an HR investigation into complaints made about him in the workplace. The Information Commissioner’s Office (ICO) confirmed the departure of New Zealand-born Edwards on June 19. It revealed that the investigation had concluded that there was a case to answer and “made clear that his behavior fell short of the conduct expected from a public official.” The secretary of state for science, innovation and technology, Liz Kendall, shared more details of the case on LinkedIn. “I have seen evidence of the vulgar and highly sexualized language that was used in his interactions with his staff and am extremely concerned that he continues to describe these incidents as misplaced humour, including on his social media post announcing his resignation,” she wrote. “Such conduct does not belong in the workplace, least of all exhibited by the leader of an organization.” Read more on the ICO: UK's Data Watchdog Gets a Makeover to Match Growing Demands. Kendall went on to thank those who came forward to share their experiences with investigators. “Multiple women shared testimony to the investigator on feeling offended, shocked and uncomfortable following interactions with Mr Edwards,” she added. Although it initially released only a brief statement short on detail about the case, the ICO posted an update on June 20, following Kendall’s post. “Mr Edwards' actions were completely at odds with our values. We do not accept sexual harassment, bullying or discrimination in any form and have clear policies in place to deal with issues such as these,” it said. “We're committed to ensuring a safe culture where all staff are able to raise concerns, knowing they will be taken seriously and trusting that action will be taken where appropriate. This must include concerns raised about the behavior of the holder of the important and privileged role of information commissioner.” Edwards Describes “Untenable” Position Edwards himself took to LinkedIn admitting that his position had become untenable “From the time the investigation was launched, I have accepted that there have been occasions where I exercised poor judgement and made attempts at humor that were inappropriate and caused offence,” he said. “It is for this reason that I have decided that it is appropriate that I resign from my position.” Edwards then spoke about the need to “continuously adapt our collective efforts to ensure safety, accountability, and trust online” as the “AI tsunami breaks over us.” Edwards, who now has an “open to work” banner on his LinkedIn profile, had comments turned off on the post. One of the more controversial chapters of Edwards’ four-year reign as information commissioner was his introduction of a new policy for public sector organizations. This saw the ICO reduce fines for erring public sector bodies and focus more heavily on reprimands, which some experts branded unfair and misguided.
infosecurity-magazine.comJun 22, 2026extracted
UK's information commissioner resigns over ‘inappropriate humour’
UK's information commissioner resigns over ‘inappropriate humour’ John Edwards, Britain's Information Commissioner, announced his formal resignation on Friday after voluntarily stepping back from his duties in February amid a workplace investigation into unspecified conduct. Writing on LinkedIn, Edwards said that while he has not agreed with how the investigation into him has been conducted, he has come to accept that his position “has become untenable.” “From the time the investigation was launched, I have accepted that there have been occasions where I exercised poor judgement and made attempts at humour that were inappropriate and caused offence,” he wrote. “It is for this reason that I have decided that it is appropriate that I resign from my position.” He said he had notified Ian Murray, the minister for digital, government and data, of his resignation as Information Commissioner and as Chair of the Information Commission, effective immediately, adding that he did not wish to be “a distraction to the ICO's important work.” Edwards, a New Zealand lawyer who served as that country’s Privacy Commissioner from 2014 to 2021 before being appointed to the U.K. role, took up the post in January 2022. He had continued to draw his £200,000 annual salary while withdrawn from his duties, despite moving back to New Zealand, as reported by Politico. Because the Information Commissioner is a statutory role accountable directly to Parliament, Edwards’ decision to step aside in February left his statutory functions without their designated holder, forcing the regulator into temporary governance arrangements. His deputy, chief executive Paul Arnold, took on those responsibilities and was designated temporary acting accounting officer for the office. Edwards agreed to step back from all contact with ICO staff and not to enter its offices while the investigation proceeded. As the commissioner is accountable to Parliament rather than employed by the ICO, the next steps — including the search for a successor — will be determined by the Department for Science, Innovation and Technology (DSIT). A government spokesperson did not immediately respond to a request for comment. Edwards’ departure comes at a transitional moment for the regulator, which is set to be replaced by an Information Commission in the future, with its functions, staff and ongoing matters transferring to the new corporate structure. Edwards would have become the chair of the Information Commission’s board. It is understood that the investigation into him contributed to the transition stalling. The delayed reforms come as the numbers of regulatory investigations launched by the ICO have dwindled, from more than 2,000 in 2019 — the first year for which data is available — to just over 200 in 2025. More than 3,000 potential cases have not yet been assigned, including 133 dating back to 2023. Alexander Martin is the UK Editor for Recorded Future News. He was previously a technology reporter for Sky News and a fellow at the European Cyber Conflict Research Initiative, now Virtual Routes. He can be reached securely using Signal on: AlexanderMartin.79
therecord.mediaJun 19, 2026extracted
NY man charged after harassing college student with AI-generated nudes
A New York man faces cyberstalking charges after allegedly sharing AI-generated nude images and fabricated racist messages using fake social media profiles to harass a Georgia college student. 21-year-old Anthony Belford was arraigned June 10 after a federal grand jury returned an indictment charging him with one count of cyberstalking. Belford and the victim had attended the same college during the 2023-2024 academic year. After the victim transferred to a Georgia college in August 2024, Belford allegedly knew of the move and began targeting the victim there. According to court documents, between January and March 2025, the defendant created fake Instagram, LinkedIn, Reddit, X, Strava, and Yahoo accounts to impersonate the victim and distribute AI-generated nude images and spread false claims that the victim had made racist remarks about black students and anti-Muslim statements. Belford allegedly created a fake LinkedIn profile using an AI-generated nude image of the victim as its profile picture, and also used a spoofed Yahoo email account to send an AI-generated nude image of the victim to the victim's mother. The defendant allegedly targeted the victim while attending the same college in the 2023-2024 academic year, but continued doing it even after the victim transferred to a Georgia college in August 2024. "Belford allegedly waged a lengthy online campaign, hiding behind spoofed social media and email accounts to harass, intimidate, and cause substantial distress to his victim with racist messages and AI-generated nude images," said U.S. Attorney Theodore S. Hertzberg. "Cyberstalking and other forms of online abuse, just like physical violence, can ruin lives and disrupt communities. Victims of such crimes should not suffer in silence, and we will continue to work with our law enforcement partners to hold the perpetrators of these crimes accountable using all available tools." The Justice Department added that federal law prohibits sharing or threatening to share intimate images (including AI-generated ones) without consent and urged victims to report violations to the FBI and to alert the Federal Trade Commission if online platforms fail to remove such content within 48 hours of a removal request. More information on how to protect yourself from cyberstalking attempts and stop the spread of images and videos shared online without consent is available on the FTC's Take It Down platform. In March, 22-year-old Jamarcus Mosley from Alabama also pleaded guilty to cyberstalking, extortion, and computer fraud charges after hacking into the social media accounts of hundreds of young women. The same month, 26-year-old Kyle Svara from Illinois also pleaded guilty to hacking nearly 600 women's Snapchat accounts to steal private nude photos that were later traded or sold online. Overall prevention scores can hide what happens after initial access. Once attackers are using valid credentials, prevention drops sharply. The Blue Report 2026 measures defenses technique by technique across 338 million simulations run in customer production environments. Get the report
bleepingcomputer.comJun 19, 2026extracted
Sanción de la Comisión Europea a Temu por incumplimientos del Reglamento de Servicios Digitales
Sanción de la Comisión Europea a Temu por incumplimientos del Reglamento de Servicios Digitales 18/06/2026 Jue, 18/06/2026 - 13:33 La Comisión Europea anunció a finales de mayo de 2026 la imposición de una multa de 200 millones de euros a Temu por incumplimientos del Reglamento de Servicios Digitales (Digital Services Act, DSA). El caso se centra en la presencia y comercialización de productos ilegales o inseguros dentro del mercado digital de Temu, una cuestión que la Comisión consideró suficientemente relevante como para abrir un procedimiento formal. La actuación se enmarca en los esfuerzos de la Unión Europea por reforzar la protección de los consumidores y aumentar la responsabilidad de las plataformas digitales que operan en el mercado comunitario.&nbsp; La decisión se basa en que Temu no habría evaluado adecuadamente los riesgos asociados a la venta de productos ilegales o potencialmente peligrosos a través de su plataforma. La Comisión Europea concluyó que existía una probabilidad significativa de que los consumidores europeos encontraran artículos que no cumplían los requisitos legales o de seguridad establecidos en la Unión Europea. Los principales afectados por esta situación fueron los usuarios y consumidores que adquieren productos a través de la plataforma, al verse expuestos a mercancías que podrían no ajustarse a la normativa vigente. Como consecuencia de estas conclusiones, la Comisión impuso una sanción económica de 200 millones de euros. Además, la empresa deberá presentar y aplicar medidas correctoras destinadas a reforzar sus sistemas de gestión de riesgos, supervisión y control de los productos comercializados, con el objetivo de adecuar su funcionamiento a las obligaciones establecidas por la DSA. En la actualidad, el procedimiento se encuentra en una fase de cumplimiento de las medidas exigidas por las autoridades europeas. La Comisión Europea ha mantenido vigente la obligación de que Temu adopte acciones correctivas para subsanar las deficiencias identificadas durante la investigación. La empresa ha manifestado públicamente su desacuerdo con algunos aspectos de la decisión, aunque la sanción y los requerimientos regulatorios continúan siendo efectivos.&nbsp; &nbsp; Referencias 06/04/2026 thecyberwire.com EU fines Temu 200 million Euros for breaching the DSA. 28/05/2026 huffingtonpost.es "Un cliente de incógnito": así encontró la UE pruebas para multar con 200 millones a Temu por no evitar la venta de "productos ilegales 28/05/2026 europa.eu Commission fines Temu €200 million for breaching the Digital Services Act Etiquetas Ciberdelito Tienda online
incibe.esJun 18, 2026extracted
AI and Cybersecurity – Everything You Wanted to Know, But Were Afraid to Ask
To better understand the current state of artificial intelligence (AI) in cybersecurity, SecurityWeek spoke with dozens of security practitioners, researchers, vendors, analysts, and AI experts. The result is a comprehensive snapshot of how AI is being used across the security landscape today. Organized into five key topic areas, this report examines the role of AI through multiple lenses: whether it can be trusted, how organizations are using it, how it can be misused by legitimate insiders, how it is being exploited by cyber adversaries, and where the technology is likely headed next. The five topics are: Generative AI (gen-AI) Agentic AI Shadow AI Machine learning (ML) Artificial general intelligence (AGI) Taken together, these perspectives provide a practical assessment of AI’s opportunities, risks, and likely evolution in cybersecurity. Generative AI Generative AI (gen-AI) is the bedrock of contemporary AI, although it is technically and potentially born out of earlier machine learning (ML, see below). It does what it says: it generates new content (most commonly text) from an AI model (most usually a large language model or LLM). Chatbots are the users’ interface to the LLM, enabling questions (known as prompts) to be applied and responses received in natural language, and answers to be received in natural language. Chatbots are the interface, and LLMs are the reasoning engine. For most people in most direct use the two seem inseparable – just one big gen-AI application. “Gen-AI trains on massive data sets, learns statistical and relationship patterns, and then uses those patterns to synthesize original output from a prompt,” explains Ahmad Shadid, co-founder and CEO at ORGN.com. This is important. It does not create factually correct answers to prompts; it predicts probable answers based on the relationship patterns it has learned – but it does create linguistically correct and compelling responses. Four deep learning architectures power the training for modern gen-AI variants. Transformer architecture (the ‘T’ in GPT and BERT) is used for the LLMs such as ChatGPT, BERT and Claude. Diffusion training generates the variants that focus on creating high quality images and also audio and video. Fundamentally, this process starts with random noise. Mathematically (guided by the user’s prompt) it reduces and reshapes the noise into the required clear result. Diffusion reverses the process of destruction. The generated result is again based on probability – in this case, the probably correct distribution of pixels. Classic diffusion is evolving into diffusion transformer technology (Sora) and ‘flow matching’ (DALL-E 3 and Midjourney) which can be described as next-gen diffusion. Generative adversarial networks (GANs) are trained via two adversarial networks locked in a feedback loop. One creates fake data, while the other learns to detect flaws by repeatedly suggesting flaws and feeding them back to the creation. Both improve until the detector can find no more flaws in the creation. This approach is good at creating images, video and audio, but has largely been superseded by diffusion technology for business use. However, criminals still use GAN-based simple, fast, real‑time face‑swap and voice‑clone models to create deepfakes. The fourth architecture, variational autoencoders (VAEs), use an encoder-decoder architecture for synthetic data generation, data compression, and anomaly detection. “Their main applications are in medical imaging and molecular generation for drug discovery,” comments Shadid. Trust in gen-AI “Gen-AI is a prediction engine. It generates what’s statistically plausible based on patterns it has seen before,” explains Emanuel Salmona, CEO and co-founder at Nagomi Security. “This makes it good at exploration: generating exploit hypotheses, trying different inputs, and connecting a strange behavior to known vulnerability patterns,” expands Albert Ziegler, head of AI at XBOW. “It’s a tool companies can use to automate creative labor,” adds David Karandish, CEO and founder at Capacity. And because of this, “It is becoming closely embedded into security teams’ workflows, from summarizing incident reports to helping draft response plans,” continues Devvret Rishi, general manager of AI at Rubrik. Galina Kho, chief strategy officer at Cyberbay, describes the advent of gen-AI as an efficiency revolution. “It’s not that entirely new capabilities have emerged; it’s that existing ones have become dramatically easier to execute at scale.” The biggest question in the use of AI is whether you can trust an output that is based on probability rather than grounded in known truth. The answer here is 56 shades of ‘No’. “It can be considered both trustworthy and not trustworthy, depending on the intent, the models used and the overall data flow involved,” comments Melissa Ruzzi, senior director of AI at AppOmni. “Gen-AI is not inherently trustworthy,” says Yichuan Zhang, CEO and co-founder of Boltzbit. “It is prone to hallucinations (confident but false statements) and data leakage (reproducing the training content or the context content exactly).” Trever Falconi, director of security and IT operations at HOPPR, explains, “Deploying a gen-AI model is not like installing software. A model trained at one institution will behave differently at another because it learned from a specific set of data and workflows. Move it somewhere new and you’ve introduced a distribution shift: the real-world data it now encounters no longer matches what it was built on, and performance quietly degrades.” Trustworthiness is a complicated question, suggests Aaron Sant-Miller, VP of AI at Booz Allen. “The model is making its best guess at the right response, but it’s not perfect.” Since gen-AI is the bedrock of all AI, there is a trickle-down effect of its strengths and weaknesses into both agentic AI and shadow AI discussed later. Cyber defenders should always be aware that gen-AI can produce errors; but that should not prevent its use. However, as Ruzzi stresses in quoting from Henri Thiel’s 1971 book (Principles of Econometrics), “Models are to be used, not believed. AI should assist analysts, not replace judgment.” The danger is that human nature drives people to believe anything that is said with confidence, and gen-AI can outright lie with confidence. Randell McNair, an adjunct professor at Florida Polytechnic university, explains on LinkedIn, “[Gen-AI] is for all practical purposes a ‘smart’ kid that has been told its whole life it is ‘brilliant’ when in fact, it is just a nearly-8 year old that has never experienced (felt the pain of) a single tangible consequence for being wrong, and has no memory of having ever truly failed someone and had to genuinely regret the shame and embarrassment that should be part of the ‘learning from failure’ process.” Gen-AI use Zhang suggests three areas where gen-AI use offers benefit: SOC productivity (summarizing complex incident logs and writing initial draft reports); secure coding (assisting developers with boilerplate code that adheres to security standards); and vibe coding (assisting non-developers with coding software applications from scratch). “Many enterprises use these models to generate documents, write articles, generate software, or replicate the messages a human would send when orchestrating a larger workflow,” says Sant-Miller. “It helps draft emails, summarize information and reduce manual effort,” adds Travis Springer, president at Sagiss. “Medical imaging teams are piloting vision-language models to surface findings from imaging studies,” says Falconi, “and researchers use synthetic data generation to fill gaps where real patient data is scarce or sensitive to use at scale.” New uses for gen-AI are continually being developed, but within cybersecurity, the most effective use comes from agentic-AI (see below) which can transform gen-AI from a passive responder into an active engager. Gen-AI misuse The misuse of gen-AI within enterprises is usually unintentional: it emanates from a failure of governance around the technology. Ungoverned use of gen-AI is always a misuse of AI. Individuals begin to rely on AI to provide quick (but not necessarily accurate) answers to questions or problems. If an AI model is deployed across the company without adequate control over its use, this can lead to a degradation of personal skill levels and an ungoverned increase in costs (the idea that AI is cheap is wrong). If access to a chatbot is not provided, employees will use external services with even less control (see shadow AI below). The problem comes from both individuals and management treating AI as a solution rather than an assistant. For example, there is potential to use AI’s coding capability to reduce the number of expensive qualified programmers. Anyone who can prompt an AI can now produce a program – but such programs will inevitably introduce new vulnerabilities. This problem goes away if qualified people use AI as an assistant, a tool to improve performance, rather than a means to reduce expensive headcount. Governance is the key to preventing the misuse of gen-AI. Gen-AI abuse By abuse, we mean bad actor use. In cybersecurity, bad actors always adopt new technology at a faster rate than legitimate business. This has certainly been true with AI. The primary reason is the power and complexity of AI. When an enterprise develops an internal AI application, it must be certain to get it right or face a possible self-inflicted catastrophe. This takes time. Criminals don’t have this concern. If something they implement doesn’t work perfectly, they just start again at no disruptive cost. The result is that new attacks tend to appear before adequate defense appears – the defenders may expect the attacks but have no detailed knowledge of them before they start. Zhang highlights three primary examples of gen-AI abuse: hyper-realistic phishing (eliminating the grammar/spelling ‘tells’ of traditional phishing); polymorphic malware (using gen-AI to subtly rewrite malware code to bypass signature-based detection); and vibe coded phishing websites and/or aggressive attacking software (using gen-AI to subtly rewrite apps that look like the original apps, but steal the user’s sensitive data). Gino Sciretta, CEO at BranditScan, warns, “Generating a convincing fake identity now takes seconds. Detecting one reliably still requires specialized tools and trained analysts. Most platforms and most users are not equipped for that. The technology has outpaced the safeguards, and the gap is widening, not closing.” Gen-Ai has introduced a step change in the quality of adversarial social engineering. It can be used to profile an individual by analyzing any social media footprint, and to then develop a targeted lure. It can build a compelling backstory to the attack, and prepare a false or disguised website to capture personal data. “Gen-AI makes mass targeted phishing, malware iteration and vulnerability research much more accessible to bad actors. Tools like WormGPT strip out the safety guardrails entirely, so attackers get the same speed advantages as regular GenAI but without the friction,” comments Harshit Agarwal, co-founder and CEO at Appknox. Image and voice cloning, and video generation is creating a deepfake scenario that increases a BEC and VEC threat that will only escalate in scale and sophistication. “Ninety-four per cent of AI-generated images had visual artifacts, but those artifacts were so subtle that the majority of targets never noticed them,” adds Sciretta. “The telltale signs are there if you know where to look, such as inconsistent light reflections in the eyes, where one pupil reflects a window and the other reflects something entirely different. But consumers are not trained to look for that, and the generators are improving faster than public awareness.” But he adds, “The most dangerous development is not the fake photos. It is the fake conversations. AI-driven chat systems can now sustain emotionally convincing dialogue over days or weeks, accelerating emotional manipulation roughly 300% faster than a human operator could.” As Ted Miracco, CEO at Approov, says, “The danger isn’t just what AI can do; it’s how fast it acts before anyone notices.” For now, criminals are primarily using AI to improve what they already do: more efficient social engineering, discovery of vulnerabilities in code, and generation of exploits. The next step will be automating the complete process of attack through agentic AI systems. Gen-AI future Amara’s law (Wikipedia) states, “We overestimate the impact of technology in the short run and underestimate the effect in the long run.” The difficulty with AI is that the short run could be next week, while the long run is probably just a few months. By the time most people really understand what is happening, what is happening has already changed. Nevertheless, some brave experts have held a finger to the wind and given their predictions. Ronan Murphy, chief data strategy officer at Forcepoint, believes, “Gen Al will be embedded in everything – every spreadsheet, every video, every workflow. The distinction between ‘using AI’ and simply ‘doing your job’ will essentially dissolve. For security teams, that means the surface you’re trying to protect keeps expanding, probably faster than your policy framework can keep up.” Zhang sees a future with SLMs (small rather than large language models). “We are moving toward ‘small language models’ that are hyper-specialized for specific domains (like a model trained exclusively on Linux kernel vulnerabilities) to reduce noise and increase accuracy.” Sant-Miller is more circumspect, wondering if the very nature of current AI makes its future indeterminable. “The future of gen-AI is a complicated one,” he says. “Models continue to get larger and, accordingly, more powerful. But there are two oppositional forces. Larger models are more expensive – both to train and to use – so capability comes at a cost. And models are trained off human generated content that provides a proxy on human reasoning. What then when most of the content is AI generated and no longer provides that proxy. These are the big questions we need to resolve as an industry.” Agentic AI Agentic AI is an evolutionary extension of chatbot gen-AI. Simplistically, a user asks the chatbot a question and then behaves in accordance with the answer received. With agentic AI, the gen-AI returns its answer to an agent, which can then instruct other organizational tools to fulfill the required behavior. But agentic AI is far more complex than this simple view – it is a task controller (or decision-maker) that uses an LLM as the primary cognitive source. The agent, or agents, are dynamic, stateful and adaptive, goal-driven and aware of the tools it or they can use to fulfill the goal. “Agentic AI converts LLMs that answer questions into software that automates the execution of work,” explains Eric Syphard, executive lead for AI at Booz Allen. “Think LLMs with hands.” Technical breakthroughs in long-memory context, tool use and evaluation enable agentic systems to complete complicated multi-step processes with little to no human oversight. “This isn’t just a new version of AI,” he continues, “It’s an entirely new operating and economic model for delivering labor: ‘labor as software’.” Miracco adds, “Agentic AI doesn’t just answer questions, it can also act autonomously on your behalf. By calling APIs, running code, managing workflows, making decisions, the LLM is now the brain controlling anything it has been granted access to, such as your phone.” Agentic AI is a meaningful step beyond gen-AI. “Rather than responding to a single prompt, an agent reasons, plans and acts. This often happens across multiple tools, data sources and application integrations, with minimal human involvement at each step,” explains Murphy. “You give the agent a goal, not an instruction, and it figures out how to get there.” Trust in agentic AI Since agentic AI uses gen-AI for cognition, it inherits the gen-AI trust issues, but with greater danger from direct access to company assets coupled with the potential for autonomous action on those assets. Can it be trusted? “It depends entirely on how it’s built. An autonomous agent with unrestricted access to your systems is a liability (see OpenClaw). An autonomous agent with scoped permissions, human approval workflows, audit trails, and budget controls is a tool you can actually rely on. Agentic systems must be transparent to more than one user,” says Marcel Folaron, CEO at Cochat. He adds, “The trust question isn’t binary. It’s architectural. Can you see what the agent did? Can you control what it’s allowed to do? Can you review its work before it takes consequential action? If yes, you have a trustworthy system. If no, you have a risk.” Can it be trusted? “Only if it is actively governed, which most organizations are not today equipped to do. Agents need broad access to function, and once that access is granted, the output rarely gets reviewed or reduced,” warns Agarwal “They bypass the UI layer entirely, interfacing directly with APIs in ways that don’t generate the session data or behavioral signals that security teams use to detect anomalies. This removes traditional visibility, especially in API-driven and mobile-first environments. Their traffic also looks legitimate, often not appearing in the logs anyone is actually monitoring.” Syphard adds, “Establishing trust requires robust identity and access governance, treating agents as nonperson entities with unique identities that must be continuously authenticated, authorized, audited, and monitored – much like human users – as agents can introduce insider threat-like risks.” Kho suggests, “Trust in agentic AI comes from how well it’s constrained. It doesn’t come from how good the model is. Therefore, the most important question is not how accurate it is, but what is the worst thing it can do if it’s wrong. Because in practice, risk is defined more by permissions than by performance.” You Mon Tsang, founder and CEO at ChurnZero, agrees with the need for governance to ensure trustworthy agentic AI. “Trust has to be earned through containment: considered data access, human-in-the-loop checkpoints, and logging everything” Zhang adds, “Trust is a major hurdle. Because agents can execute actions (like deleting a user or changing a firewall rule), they require strict guardrails and ‘human-in-the-loop’ checkpoints to prevent runaway processes… it is very important to have the guardrails in place for any agentic AI.” A ‘human in the loop’ is an important part of the governance mechanism that allows trust in agentic AI. But it’s a moving target. As the quality of AI, the speed of doing business, and the volume and pace of attacks all increase, so the pressure to reduce the level of human constraint over agentic action also grows. Continuously ensuring the correct balance between human and autonomous action is an important factor in maintaining maximum performance with maximum trust. Agentic AI use Current implementation of agentic AI is cautious but accelerating: cautious because most organizations understand this is a beast that is difficult to tame; accelerating because the benefits are real. The ability to act at machine speed with minimal human activity is a boon to cybersecurity. Zhang cites the potential for ‘autonomous patching’. “An agent identifies a vulnerability, finds the patch, tests it in a sandbox and deploys it,” he says. “It’s being used for workflow automation, assistants, ticket triage, and research support. In security teams, AI is primarily helping analysts gather context, not make decisions,” adds Kho. “Enterprises use agentic AI for tasks that are repeatable, time-consuming, and currently falling through the cracks – monitoring, reporting, data aggregation, alert triage, content generation, compliance checks… The value is highest for small and mid-size teams that lack the headcount to do everything manually,” says Folaron. “Enterprises are already deploying agentic AI to write code, triage security alerts, manage infrastructure, and automate workflows that previously required entire teams. The productivity gains are very real,” adds Jim Sherlock, VP of AI & cybersecurity R&D at ProCircular. “For enterprises, the real opportunity is closing the gap between finding a problem and actually resolving it. That gap – the investigation, the cross-team coordination, the verification that a fix actually held – has been almost entirely manual for decades,” says Salmona. “Agentic systems are starting to absorb that work. But the ones doing it well are grounded in deep environmental context. The ones that aren’t grounded in context are generating activity without reducing exposure. Those are very different things.” Agentic AI misuse Misuse of agentic AI is generally accidental, rooted in its lack of governance, guardrails, and careful design, and exacerbated by the unpredictability of machine reasoning. A never-ending logic loop (continuously striving but never succeeding) could keep the agent running effectively forever unless manually halted. Such never-ending loops could be caused by hallucination, bad design, or a failure of the agent/LLM to recognize that its goal has already been achieved. “An important aspect of trust in AI agents is training them to know their limits. No one wants to be stuck in an endless loop when a human could easily step in and solve the problem,” comments Karandish. “The problem that keeps me up at night is simple: an agent is only as good as the context it operates on,” adds Salmona. “Give it an accurate, correlated view of your environment – your assets, your controls, your exposures, your threat landscape – and it can make decisions that genuinely reduce risk. Give it incomplete data and it will still act. Confidently. Quickly. Incorrectly. Automation without verified context is just a faster way to be wrong at scale.” It is this type of accidental misuse of agentic AI that feeds the widespread trust problems. “For agentic AI to succeed in the future, safety, governance and recoverability must be top priorities,” warns Rishi. “The unintended consequences are real. Agents can drift – taking actions that technically follow their instructions but produce outcomes nobody intended. They can accumulate permissions over time if nobody’s auditing them,” adds Folaron. Agentic AI abuse The complex reality of agentic AI is that while it benefits enterprises, it simultaneously increases their attack surface – and that bad actors both attack agentic systems and use their own agentic systems to speed and scale their attacks. To make matters worse, enterprises are often unaware of the expanded attack surface – downloaded apps are sometimes provided with built-in, but unspecified, agentic systems. “As for the bad actors, right now, the most common ways they are using AI are to conduct old-school attacks at a much faster rate or publish malicious AI projects to infect early adopters riding the hype. But over time, as AI gets into more critical systems and companies give their internal agents more authority, we are going to see a lot more prompt injections used to manipulate these systems,” adds Amit Chita, field CTO at Mend.io. Bad actors target the agentic attack surface in multiple ways, most commonly via prompt injections. “Prompt injection attacks can quietly redirect an agent to exfiltrate data or build delayed-execution payloads from inputs that looked harmless on arrival,” warns Agarwal. “In my view,” comments Shadid, “cyber offenses will become near-fully agentic within one to two years. Defense will have to become autonomous to match.” Ron Longo, CEO at TrustLogix, suggests, “Cybercriminals will leverage the sheer scale and intelligence of agentic AI to launch more advanced and overwhelming phishing and malware attacks. Because agentic AI can be autonomous, it can automate and orchestrate these attacks with greater sophistication than in previous eras of cybercrime.” We’re not there yet. “They don’t need full automation. Even a partial automation significantly increases their efficiency and return on effort,” explains Kho. But it’s going to get worse. “Agentic AI enables attackers to automate reconnaissance, vulnerability discovery, exploitation attempts, and adaptation across many targets at once. Instead of just generating content, it can pursue an objective across multiple steps,” says Ziegler. “In other words, the shift is from AI generating artifacts to AI conducting operations.” Murphy adds, “The concern looking ahead is agentic systems that can identify a weakness autonomously, exploit it, exfiltrate data and cover their tracks, all without a human in the loop on the attacker’s side. We’re not fully there yet. But the trajectory is obvious, and the security industry is not moving fast enough to get ahead of it.” That trajectory has already been confirmed by Anthropic’s discovery of a largely automated attack from a China-linked state-sponsored threat actor in November 2025. “Instead of a human hacker manually probing a system, an AI agent can scan for vulnerabilities, test exploits, exfiltrate data, and cover its tracks – all without human intervention. Spear-phishing campaigns that adapt in real time based on the target’s responses. Automated reconnaissance at a scale that wasn’t possible before. The same autonomy that makes agents useful for defenders makes them dangerous in the wrong hands,” says Folaron. Agentic AI future “Given the potential productivity impact of agentic AI, I am confident it will become a core part of how businesses are run,” says Tsang. Within cybersecurity, “We will likely see the rise of ‘agentic orchestration’, where multiple specialized agents (a ‘detection agent’ and a ‘remediation agent’) collaborate to manage entire security lifecycles” suggests Zhang. But the complexity of agentic will need to be matched by complex controls. “What I’m certain about is that static, rule-based controls won’t keep pace. You need data security that understands context – what the agent is doing, what data it’s touching, what risk that represents – and adapts dynamically. This idea of adaptive security is so critical for today and for tomorrow. The old ‘block or allow’ binary doesn’t work when an AI agent is making hundreds of data decisions per minute,” warns Murphy. “The future is agents that run continuously, learn from their results, collaborate with each other, and only surface to humans when a decision requires judgment. But that future only works if we solve governance first. Autonomy without accountability is a disaster waiting to happen,” says Folaron. One area that is still heavily debated is the degree of autonomy that will be allowed in future agentic systems. “In the future, agentic AI will be successful where governance is strong, but risky where automation is mistaken for maturity. It should be supervised automation, backed by clear boundaries and continuous validation. The future isn’t autonomous security,” says Kho. “I expect more systems built from many short-lived agents with narrow goals, persistent coordination, strict policy controls, and independent validation,” says Ziegler. “Agentic performance is not just about picking one favorite model forever; sometimes different models contribute different strengths at different points in the loop. The real frontier is not ‘more autonomy at all costs.’ It is autonomy that remains auditable, evidence-driven, and safe to operate in production.” Shadow AI Shadow AI is AI installed within the enterprise but unknown to the IT and security departments, or external AI used by an employee without reference to the IT and security department. “Shadow AI is the cybersecurity version of shadow IT, except the blast radius is orders of magnitude larger. It enters enterprises the same way every unsanctioned tool does,” comments Sherlock. Agentic shadow AI usually enters when an employee finds an open source tool and installs it to improve his or her work performance. However, “Unlike shadow IT, shadow AI operates inside workflows, not outside them. That makes it harder to detect and easier to trust” warns Agarwal. This is especially pertinent when the AI is included but undisclosed agents within a downloaded cloud SaaS app. If these apps are installed, they can arrive with one or more pre-approved valid OAuth tokens granting access to different parts of the customers’ infrastructure. If an attacker gains access to such an OAuth token, that attacker gains easy access to frequently sensitive information. The potential extent of this access can be massive – as seen in the Salesloft Drift compromise in 2025. Drift is an AI chatbot and website engagement tool for Salesforce. Attackers stole its OAuth tokens, gaining access to organizations that installed Drift. Subsequently, more than 700 organizations were compromised via the shadow AI within Drift. If any of those organizations were unaware of the agentic AI within Drift, they were effectively compromised by shadow AI. A further example of shadow AI occurs when an employee uses an external chatbot, without the security department’s knowledge, to access gen-AI. That employee could then perform actions inside the organization based on incorrect, inadequate or simply hallucinated information. Nevertheless, “The productivity benefits [of using shadow AI] are real, and I want to be clear about that,” says Murphy. “People aren’t using these tools because they’re reckless. They’re using them because they work. The problem is that productivity gains and data risk are happening simultaneously, and organizations frequently have visibility into neither.” Shadow AI trust Ultimately, there can be no trust in shadow AI. What cannot be seen, cannot be trusted. “Models that haven’t been vetted can be manipulated, can inherit biases from unvetted training data, or can behave unpredictably when they encounter inputs outside their training distribution. And because no one is monitoring them, that unpredictability goes undetected,” warns Falconi. Shadow AI use “Shadow AI is what happens when good intentions meet convenience. An employee discovers a new AI tool – a browser plugin, a code assistant, a productivity app – and starts using it because it genuinely helps them get work done faster,” explains Murphy. In the short term, shadow AI can benefit the company. But in the long term, “The risk of a massive data breach or regulatory fine (GDPR/CCPA) far outweighs the efficiency gains,” adds Zhang. “People start using shadow AI because it genuinely helps them work faster. The problem is that the productivity gain comes with unquantified risk. You’re trading speed for control, and you often don’t realize what you’ve given up until something goes wrong,” says Folaron. Shadow AI misuse Strictly speaking, any and all use of shadow AI is a misuse of AI, simply because it hasn’t been sanctioned by the company. This misuse can cause serious problems, albeit accidental. “In healthcare, the scenario plays out regularly,” comments Falconi. “A radiologist finds an open-source model and starts using it to help triage scans. A researcher pipes imaging data through a consumer AI tool to accelerate analysis. Nobody in IT, security, or compliance knows it exists. There’s no audit trail, no documented provenance on the data it’s touched, and no version control.” The compliance issue is magnified within shadow AI – it can cause serious regulatory issues. “When something goes wrong, there is no way to trace it, contain it, or demonstrate to a regulator that reasonable precautions were taken.” The regulatory exposure varies by industry, but the accountability gap is consistent. “In healthcare, that’s a compliance failure, a potential HIPAA liability. In financial services, it implies SEC and FINRA oversight. In any organization handling EU data, GDPR applies. Across all of these regulations, the legal position is the same: an enterprise that cannot document how an AI system was built, validated and monitored has no defensible posture when that system causes harm,” he adds. However, “The security implications go beyond compliance gaps. When employees use unsanctioned AI tools, sensitive data often leaves the organization’s perimeter entirely, fed into external APIs or platforms with opaque data retention policies. Unlike traditional shadow IT, the exposure isn’t just a misconfigured tool. It’s proprietary or protected data potentially being ingested into systems that the organization has no visibility into and no contractual control over,” continues Falconi. “These tools often use ‘public’ settings, meaning any sensitive data entered (like proprietary source code or customer PII) becomes part of the vendor’s training set, effectively leaking it to the public,” explains Zhang, adding, “Bad actors look for exposed API keys or ‘leaked’ company secrets within public AI datasets to gain a foothold in the target network.” And Geoff Mattson, CEO at SecureAuth, warns, “When someone configures an MCP server on their laptop to give Claude access to internal databases, that’s shadow AI with real teeth.” Shadow AI abuse “Shadow AI is more of an attack surface than an attack tool,” comments Folaron. The biggest problem introduced by shadow is this larger attack surface: “Every unsanctioned AI integration is a potential data leak, a potential compliance violation, a potential entry point. The risk is structural, not just behavioral,” continues Murphy. Unsanctioned tools running inside an enterprise perimeter are, by definition, unmonitored. “That makes them a viable vector for malicious insiders. An employee using an unvetted tool to exfiltrate data, manipulate outputs, or conduct competitive intelligence with little risk of detection is risky. Because shadow AI exists outside formal IT systems, the usual tripwires aren’t in place,” expands Falconi. Bad actors also attempt to enlarge and manipulate this hidden attack surface by tricking employees into downloading deliberately poisoned open source models. “Someone can download and deploy a model that has been tampered with upstream, and it operates invisibly inside the enterprise. Without provenance documentation or a validation process, there’s no way to know what you’re running or whether it’s been manipulated,” continues Falconi. “In cybersecurity, problems rarely start with attacks; they start with blind spots. The issue with shadow AI isn’t in trusting it but not having full awareness of it,” explains Kho. Shadow AI future The correct future for shadow AI is known, but whether it is achievable is moot. “Shadow AI will grow before it shrinks. The tools are too accessible and the productivity incentives too strong for the trend to reverse on its own. Locking everything down doesn’t work either. Overly restrictive policies don’t eliminate shadow AI; they just drive it further underground where it becomes even harder to detect and govern,” argues Falconi. Despite the problems involved in ridding companies of their shadow AI, many practitioners believe it can and will happen. “The trajectory is predictable,” says Tsang. “IT will catch up. Organizations that move fastest to offer sanctioned, secure AI tooling will have the least shadow AI problem, because the incentive to go around IT disappears when IT is actually delivering.” Falconi agrees with this. “When organizations provide practitioners with secure, auditable platforms that offer the speed and flexibility they’re looking for, the appeal of unsanctioned tools diminishes. Shadow AI exists because the governed alternative is too slow, cumbersome, or unavailable. Fix that, and you address the root case rather than the symptom.” Salmona adds, “The organizations that solve this won’t do it by banning tools. They’ll do it by making the approved path faster than the shadow path. That’s a design problem, not a policy problem.” History, however, begs to differ. Our shadow IT (that is, IT without any AI) has been with us for many years. Not only has industry failed to solve shadow IT, but the problem is also bigger than ever. The idea that we will in time solve the shadow AI problem, which is likely to be more intransigent than shadow IT, is decidedly moot. Machine Learning (ML) Industry has been using machine learning AI systems for many years – long before gen-AI found popular usage. ML and gen-AI are related. Both are trained on data. But while gen-AI is trained on mass data scraped from the internet, ML is trained on data constrained to its primary, usually local, task. Because of the more constrained source data, the output is deterministic while gen-AI’s output is probabilistic. “Text recognition tools/systems (OCR) are a good example,” says Folaron. “They are ML tools that have been trained on thousands and thousands of papers. When you scan a document, they identify the text fairly accurately. If you scan the same page twice it will most likely give you the same output.” ML uses statistical algorithms to find anomalies in data. “In security,” says Zhang, “it is primarily used for pattern recognition and behavioral analysis.” That behavioral analysis is used to locate indications of compromise by highlighting deviations from the norm. ML trust “In general, ML is more trustworthy than gen-AI as it is used to analyze existing content, not generate new content,” says Ruzzi. However, “ML is only as reliable as what it was trained on, and models trained on incomplete or outdated data will miss threats that don’t look like past threats. Attackers know this. They study detection logic to craft inputs that stay inside the boundaries of what looks normal, effectively teaching themselves to evade the systems designed to catch them. ML systems also fail silently. When they miss, they do not alert. They normalize,” warns Agarwal. “Within its trained domain, ML can be exceptionally reliable, often more consistent than human analysts who tire, get distracted, or become overwhelmed by volume. But it has blind spots. ML models are only as good as their training data. If the training data doesn’t include a particular type of attack, the model won’t catch it,” agrees Folaron. “The honest answer is that ML is trustworthy as one layer of defense, not as the only layer. It’s excellent at reducing noise and surfacing what matters. It’s not a replacement for human judgment on critical decisions.” “ML in cybersecurity is trustworthy when it is used to augment human decision-making, not replace it,” adds Sciretta. “The risk comes when organizations treat ML as a set-and-forget solution. Models degrade over time as the threat landscape shifts. If you are not continuously retraining, validating, and auditing your models, you are building on a foundation that is slowly crumbling underneath you.” Rishi says, “The key challenge is making machine learning decisions observable and explainable. Organizations need a clear understanding of how outcomes are derived, what signals they depend on, and where those decisions can be validated or overridden, or they risk relying on decisions they don’t fully understand or control.” ML use “Machine learning applications in cyber look toward risk analysis, behavioral analysis, and threat detection. Each machine learning approach carries different tradeoffs based on the method selected under the hood. Some are less powerful but generalize to new use cases better and are more transparent (easy to explain why they said or did things). Others are more focused and black box. Those are tradeoffs an AI team balances when delivering these features,” says Sant-Miller. “ML is the foundation of many AI applications in cybersecurity. It involves using models that are trained on past data to identify patterns, spot unusual activities and highlight behavior that differs from what’s considered normal,” continues Agarwal. “Enterprises use it for threat detection, malware analysis, risk scoring and behavioral monitoring across endpoints and networks. Its value comes from operating at a scale no human team can match.” Folaron adds, “Threat detection – spotting anomalies in network traffic, endpoint behavior, or user activity. Email filtering. Fraud detection. Vulnerability prioritization – figuring out which of your 10,000 vulnerabilities actually matters. User and entity behavior analytics (UEBA) – learning what normal looks like for each user and flagging deviations. Log analysis at scales no human team could process manually.” Zhang provides a specific UEBA example: “Flagging when a user suddenly downloads 5GB of data at 3:00 am.” Ruzzi says it is used “For deep analysis of numerical content, large volumes of data, or data analysis where the intent is to be as deterministic as possible, ML is normally preferred over gen-AI, or is used as an intermediate step to analyze data to then be used by gen-AI.” Despite the potential value of ML in cyber defense, Rishi stresses, “The key challenge is making machine learning decisions observable and explainable. Organizations need a clear understanding of how outcomes are derived, what signals they depend on, and where those decisions can be validated or overridden, or they risk relying on decisions they don’t fully understand or control.” ML misuse ML doesn’t lend itself to active misuse by employees: what misuse occurs is by omission rather than commission. Salmona gives an example – model drift. “Accuracy at deployment is not accuracy six months later. Environments change, attacker behaviors evolve, and the model doesn’t automatically keep up. Most organizations have no systematic way to monitor for that degradation. They trust the tool because it worked before. That assumption will eventually cost them.” ML abuse The same advantage of automated analyses means that adversaries use their own ML systems. “Any system that helps automate selection, prioritization, or iteration can make attackers faster and more persistent.” It is a key component in the ongoing industrialization of cybercrime. “The general pattern is that cyber operations stop being bespoke and become industrialized,” says Ziegler. Attackers also use ML for evasion; “Using their own ML models to simulate a target’s security system and find ‘blind spots’ where their attacks won’t be detected,” says Zhang. “Evading detection systems by training models that learn what triggers alerts and then optimizing attacks to stay below the threshold,” expands Folaron, adding. “Automated password cracking. Generating polymorphic malware that mutates enough to bypass signature-based detection while maintaining its payload. And increasingly, using ML to prioritize targets – analyzing publicly available data to identify the most vulnerable or valuable organizations to attack.” Ruzzi adds, “Bad actors can use ML to automate reconnaissance or map network vulnerabilities.” But bad actors will also directly attack enterprise ML systems. “It is susceptible to adversarial attacks where attackers ‘poison’ the training data to make the ML model ignore specific types of malicious activity,” warns Zhang. ML future The future for machine learning is a convergence with gen-AI. “ML in cybersecurity is moving toward real-time, adaptive defense – systems that don’t just detect known patterns but continuously learn and respond to new ones. The convergence with agentic AI is where it gets interesting. Instead of ML flagging a threat and waiting for a human to respond, you’ll have ML-powered agents that detect, investigate, and contain threats autonomously within defined boundaries. Speed of response becomes the competitive advantage, because attackers are already operating at machine speed,” explains Folaron. The reasoning is clear. “Where ML is going is toward more adaptive, continuously retrained models that can keep pace with how fast attacker behavior evolves. In other words, fewer static rulesets and more real-time learning from live environments,” agrees Agarwal. “Moving from “reactive” detection to “predictive” defense where ML models can forecast where an attacker is likely to move next based on early-stage lateral movement,” confirms Zhang. However, whether ML can ingest agentic strengths without simultaneously inheriting agentic’s concerns, remains to be seen. “ML is heading toward tighter integration with agentic systems – models that both inform and trigger action. That’s where the real leverage is, and also where the risk compounds,” says Salmona. “An ML model feeding a bad signal into an automated workflow produces a wrong action at machine speed, across your entire environment, before anyone realizes something is off. Context and continuous validation aren’t optional anymore – they’re the difference between automation that reduces risk and automation that amplifies it.” Artificial General Intelligence (AGI) Many of the best known AI frontier labs, such as OpenAI, DeepMind, Anthropic, and xAI, are pursuing the idea of general artificial intelligence (AGI). “AGI is a hypothetical stage of AI capability that allows machines to replicate or exceed all dimensions of human cognitive capability. Everything from reasoning, adapting, novel concept creation, and (in theory) consciousness. With all scientific endeavors, everything feels impossible until the next breakthrough brings you closer. Two hundred years ago we didn’t have cars, and now flying across the country or to another planet feels normal. Fifty years ago, we didn’t have the internet, and now the vast majority of our communication is electronic,” explains Sant-Miller. A true and accurate definition of AGI is elusive. “I don’t really know how to define AGI, but I also don’t think it matters. Something will be built in the next few years that will leave us all in wonder. The models are improving fast enough that quibbling over the definition can’t be the point,” comments Tsang. “True AGI, with the ability to learn from experience for critical decisions, is still widely considered decades away by most researchers,” adds Zhang. Many people believe AGI will be achieved, others are less certain, but most agree that the task is daunting and the timeline obscure. “It’s neither inevitable nor impossible, and anyone who tells you they know the timeline is guessing,” says Folaron. “We’ve made remarkable progress in narrow AI, but the gap between what current systems do and what AGI requires is often understated.” AGI trust Trust in any future AGI entity will be a moral dilemma: should we trust the decisions of an entity that has vastly more knowledge and deeper intelligence than ourselves? Will it make the right decision between taking an action that would benefit hundreds while harming dozens? Everyday life is full of such dilemmas for everyone. But should we be willing to delegate the power of choice to something that is ultimately a machine? The answer will be the answer to almost all cybersecurity questions: ‘It depends’. But on what, we don’t yet know. AGI use, misuse and abuse “The practical stance is use it, and build guardrails as it gets more capable. The dangerous scenarios aren’t ones where some pundit or AI CEO declares AGI achieved. They’re ones where a highly capable system makes a catastrophic decision or is turned against targets by a sophisticated adversary. And the technology we have today is powerful enough to be very ready,” suggests Tsang. Catastrophic decisions already occur with current AI, which seems to be moving inexorably toward increasing autonomy. Guardrails are the safeguard, but they haven’t yet prevented all catastrophes. “I think the more practical question for security leaders isn’t whether we achieve artificial general intelligence, but whether we’re ready for artificial general authority. We’re already giving AI agents meaningful decision-making power over sensitive systems. The governance frameworks, identity architectures, and trust models are what need to be built right now, not after some theoretical singularity arrives,” warns Mattson. But here is another of cybersecurity’s moral dilemmas. Should we hobble a racehorse so that it cannot cause collateral bystander harm, or should we set it free to run fast and break things? Safety or potential greater business profit? “The big risk in AGI is similar to gen-AI, where the focus on functionality clouds proper cybersecurity due diligence,” comments Zhang. “By trying to make AI as powerful as it can be, organizations may misconfigure settings, leading to over-permissions and data exposure. They may also grant too much power, creating a major single point of failure,” warns Ruzzi. If AGI is ever fully realized, the effect on cybersecurity will be profound. “If AGI is achieved, cybersecurity as we know it fundamentally changes for both sides. On defense, you’d have systems that can genuinely reason about novel attacks, understand attacker intent, and adapt defenses in real time without human guidance. On offense, you’d have attackers with access to systems that can find and exploit vulnerabilities faster than any human team could patch them,” comments Folaron. “If achieved, it would be the ultimate zero day event,” warns Zhang. “An AGI could find and exploit vulnerabilities in every system simultaneously. Conversely, an AGI-based defense could theoretically create a ‘perfect’ security posture that adapts in real-time to any threat, effectively ending the era of human-driven hacking.” Rishi adds, “In an AGI world, recovery and resilience are the primary safety nets. Since even the best governance cannot predict every move a general intelligence might make, organizations must have rewind capabilities.” AGI future “We are still many major breakthroughs away from AGI. I’m far from an expert to estimate when those breakthroughs will be realized, how far they will move us forward, and what they will change. But the beauty of science is that things often thought impossible are proven to be possible,” says Sant-Miller “We keep debating whether machines can truly think. Meanwhile, they’re beating the MIT math team in problem solving, passing the bar exam, writing exploits, and running sophisticated operations. The philosophical debate is becoming irrelevant. The distance between very impressive narrow AI and AGI is narrowing faster than most people are prepared to accept. Our take is that AGI isn’t far off, but it still remains a fuzzy threshold. We may cross that threshold without realizing we’ve even crossed it,” comments Miracco. Today, the idea of AGI is magic. Tomorrow it may be science. It is not a new concept in literature, but unless we learn from today’s mistakes made in current AI’s development and use, tomorrow’s genuine AGI may really become a world of machine-versus-machine, with ever-decreasing human relevance. Amara’s law applies. The arrival of true AGI is likely to be further off than most people predict, but when it comes it will be far more beneficial and far more dangerous than we can currently imagine. Related: Shadow AI Risk: How SaaS Apps Are Quietly Enabling Massive Breaches Related: The Wild West of Agentic AI – An Attack Surface CISOs Can’t Afford to Ignore Related: AI Fuels ‘Industrial’ Cybercrime as Time-to-Exploit Shrinks to Hours Related: Cyber Insights 2025: Social Engineering Gets AI Wings
securityweek.comJun 16, 2026extracted
Chainguard, JPMorgan, BNY Team Up to Secure Open Source from AI Threats
Open-source security firm Chainguard has brought together dozens of partners in a new industry coalition to protect open-source software from AI attacks. The initiative, called Athena, was announced by Chainguard on June 16. Its founding members include BNY, Chainguard, Cisco, Cloudflare, Corridor, DepthFirst, Docker, JPMorganChase, Kyndryl, LTIMindtree and PwC. Based on preliminary work at Chainguard, Athena provides a vulnerability intelligence sharing platform and tools to fix the vulnerabilities frontier AI models, like Anthropic’s Mythos and OpenAI’s GPT-5.5.-Cyber, find before attackers can exploit them. Here’s how Athena works, according to Chainguard’s CEO Dan Lorenc: Coalition members pool vulnerabilities affecting open-source projects they have discovered and packages into the Athena platform using frontier AI programs they have access to, including Anthropic's Project Glasswing and OpenAI's Daybreak Chainguard patches them privately and affected projects are rebuilt as private, hardened versions, available to members through Chainguard Libraries before disclosure Coalition members that operate infrastructure, platform, network and security layers push non-patch mitigations ahead of disclosure so that coverage exists even where a clean patch does not yet Cybersecurity partners add their own detections, signatures and virtual patching The Athena coalition drives coordinated upstream disclosure Additionally, Chainguard hopes to work with the Linux Foundation on a coordinated Security Incident Response Team (SIRT) for open source and a maintainer of last resort program. Announcing the project on LinkedIn, Lorenc said Athena allows for every vulnerability one member discovers to get remediated and pushed upstream, “becoming a fix the entire ecosystem inherits, often before disclosure.” “And for the parts of the world that can't patch on an attacker's timeline, partners who sit in front of much of the internet push mitigations out ahead of disclosure, blocking the issue for people who never knew there was anything to block,” he added. Chainguard also highlighted that the Athena model acts as “an AI cybersecurity clearinghouse” like the one the US government has been asked to build following the Trump Administration's latest Executive Order, Promoting Advanced Artifical Intelligence Innovation and Security, published on June 2. “It’s even more relevant since the US government declared Mythos too dangerous for public access on Friday,” the open-source security company added. Athena is operational and has already processed over 20,000 findings and shipped more than 2000 patches across 500 open-source projects. The initiative will begin publishing its first wave of disclosures in July and continues to welcome new partners. “Will it be perfect? No, and no one should pretend otherwise,” said Lorenc. “But fragmentation is worse, standing still isn't survivable, and the more of the industry that's in, the less any attacker has left to find. Join us.”
infosecurity-magazine.comJun 16, 2026extracted
Compromiso de acceso en cuentas de Instagram por una vulnerabilidad en el sistema automatizado de soporte técnico de Meta
Compromiso de acceso en cuentas de Instagram por una vulnerabilidad en el sistema automatizado de soporte técnico de Meta 16/06/2026 Mar, 16/06/2026 - 12:48 Desde el 17 de abril hasta el 31 de mayo Instagram sufrió un incidente de ciberseguridad. Durante ese periodo, la compañía logró detectar la anomalía de manera oficial. Este suceso se originó debido a la explotación activa de una vulnerabilidad crítica presente en uno de los sistemas internos automatizados que la empresa utiliza para la gestión de usuarios. Durante este intervalo de tiempo, diversos actores maliciosos aprovecharon un fallo de validación en los flujos de trabajo de soporte técnico para comprometer de forma masiva y sistemática el acceso a miles de perfiles personales dentro de la red social. La vulnerabilidad se debía a un error de código en la herramienta de soporte asistida por inteligencia artificial conocida como "High Touch Support" (HTS), la cual permitía a los ciberdelincuentes solicitar enlaces de restablecimiento de contraseña hacia correos electrónicos externos no asociados originalmente con las cuentas objetivo, facilitando el secuestro de aquellos perfiles que carecían de la autenticación de doble factor (2FA). Según los datos oficiales proporcionados por Meta, un total de 20,225 usuarios de Instagram se vieron afectados globalmente por esta vulnerabilidad, comprometiéndose información confidencial como mensajes directos, datos de contacto, fechas de nacimiento y publicaciones privadas. Como respuesta inmediata tras el descubrimiento del fallo, la empresa procedió a desactivar por completo la herramienta HTS, invalidó todos los enlaces de restablecimiento generados de forma fraudulenta e implementó un punto de control de seguridad obligatorio para forzar a las víctimas a reautenticarse y cambiar sus contraseñas. En la actualidad, Meta ha declarado oficialmente que el problema técnico de seguridad ha sido resuelto con éxito y que todas las cuentas de Instagram que resultaron afectadas ya se encuentran debidamente aseguradas para evitar cualquier acceso no autorizado continuado. Asimismo, la compañía ha confirmado de manera formal que la herramienta de recuperación asistida por inteligencia artificial permanecerá inactiva hasta que se corrija definitivamente la verificación de autenticación en el punto de entrada de recuperación de cuentas. Por último, la dirección de la empresa ha anunciado que se está llevando a cabo una revisión exhaustiva y completa de todos los flujos de recuperación de cuentas similares a lo largo de todas las plataformas del grupo Meta con el objetivo explícito de identificar y remediar preventivamente cualquier otro problema potencial de la misma naturaleza. &nbsp; Referencias 01/06/2026 krebsonsecurity.com Hackers Used Meta’s AI Support Bot to Seize Instagram Accounts 08/06/2026 securityweek.com Data BreachesMeta Says 20,000 Instagram Accounts Hacked via AI Tool Abuse 08/06/2026 helpnetsecurity.com Hackers used Meta’s AI support system to hijack over 20,000 Instagram accounts 08/06/2026 siliconrepublic.com More than 20,000 Instagram accounts hacked using Meta AI bug 08/06/2026 bleepingcomputer.com Over 20,000 Instagram accounts stolen in Meta AI support hack Etiquetas Instagram Redes sociales Sistema vulnerable Vulnerabilidad
incibe.esJun 16, 2026extracted
FBI Seizes 13 Websites That Officials Say Were Used by China to Target and Recruit US Workers
The FBI has seized more than a dozen websites that officials say were part of a Chinese effort to target American workers who have access to classified or sensitive government information, the Justice Department said Wednesday. The 13 websites purported to be affiliated with consulting companies that advertised job openings for current and former holders of security clearances. But the companies were all fakes and the job postings were a sham, officials said. The internet domain seizure is part of a broader effort by Western law enforcement and intelligence agencies to sound the alarm about alleged Chinese government plots to recruit workers who can be duped into disclosing sensitive information. Last week, for instance, the English-speaking Five Eyes intelligence-sharing alliance — Australia, Canada, New Zealand, the U.K. and the U.S. — issued a bulletin warning that China is targeting personnel from those countries on job websites to get access to classified or sensitive information. The bulletin said spies for Chinese military intelligence have been posing as workers acting on behalf of private businesses or think tanks, advertising for bogus jobs such as foreign policy or defense analysts and pressuring candidates to provide “non-public” information. According to an FBI affidavit filed in connection with the website seizure, the fake websites relied on fraudulent or stolen identities and AI-generated photographs to give them the appearance of legitimacy, and advertised generic “consulting” jobs geared toward current or former U.S. government employees. “These websites are often linked or referenced within the entities’ job postings on LinkedIn and other hiring platforms,” the affidavit said. Applicants and recruits were offered money for reports related to their work and for sensitive information, the Justice Department said. The operators of the plot, who officials allege to be tied to Chinese intelligence services, used cryptocurrency and online payment systems to hide their real identities, officials said. Law enforcement officials identified the websites through information from targets who came forward to report what they believed to be suspicious interactions. “A lot of this information came from doing interviews, interviews with people who came forward that something didn’t seem right,” Dan Wierzbicki, the special agent in charge of the counterintelligence and cyber division of the FBI’s Washington field office, said in an interview. “They provided information and said, ‘Hey, this is kind of weird, we’re kind of getting paid by a cryptocurrency or an online payment system that’s not typical,’” he added. He said the FBI believes there are other websites serving a similar purpose and is seeking the public’s help in identifying them. A spokesperson for the Chinese embassy in Washington called allegations of Chinese espionage “entirely fabricated” and “malicious slander.” Related: China-Linked APT GopherWhisper Abuses Legitimate Services in Government Attacks Related: FBI Warns of Data Security Risks From China-Made Mobile Apps Related: 3 Men Charged With Conspiring to Smuggle US Artificial Intelligence to China
securityweek.comJun 11, 2026extracted
Ciberataque a los sistemas informáticos internos de Transporte Metropolitano de Los Ángeles
Ciberataque a los sistemas informáticos internos de Transporte Metropolitano de Los Ángeles 11/06/2026 Jue, 11/06/2026 - 10:33 Durante la segunda quincena de marzo de 2026, la Autoridad de Transporte Metropolitano del Condado de Los Ángeles (LACMTA), comúnmente conocida como LA Metro, detectó una actividad no autorizada en parte de su infraestructura tecnológica interna. El incidente fue identificado por los equipos de seguridad de la organización el 16 de marzo, momento en el que se activaron los protocolos de respuesta para contener el acceso indebido. Aunque la investigación continuó durante las semanas posteriores, la organización confirmó posteriormente que había sido víctima de un ciberataque que afectó a diversos sistemas administrativos. Desde el inicio del incidente, LA Metro señaló que los servicios esenciales de transporte ferroviario y de autobuses continuaron operando con normalidad y sin interrupciones para los usuarios. El ataque afectó principalmente a sistemas internos utilizados para tareas administrativas y de gestión. Como medida de contención, LA Metro restringió de forma preventiva el acceso de los empleados a numerosos sistemas corporativos mientras se analizaba el alcance de la intrusión y se verificaba la integridad de los servidores afectados. Durante este proceso se registraron incidencias en algunos servicios tecnológicos de apoyo, como paneles informativos y determinadas funcionalidades relacionadas con la gestión operativa, aunque el transporte público continuó funcionando. Semanas después, un grupo denominado Ababil of Minab reivindicó la autoría del ataque y afirmó haber destruido grandes volúmenes de datos y exfiltrado información. Referencias 26/05/2026 cybersecuritydive.com Iranian government, not hacktivist group, breached LA Metro system, security firm says 27/05/2026 securityweek.com LA Metro Cyberattack Linked to Iranian State-Sponsored Hackers 27/05/2026 securityaffairs.com The LA Metro Attack Wasn’t Hacktivism. It Was a State Operation With a Costume On. Etiquetas Ciberdelito Ferrocarril Sector transporte
incibe.esJun 11, 2026extracted
Path traversal flaw in AI dev platform Langflow exploited in attacks
Attackers are actively exploiting CVE-2026-5027, a high-severity path traversal vulnerability in the AI development platform Langflow, to write arbitrary files on exposed servers. Langflow is an open-source visual platform for building AI applications, AI agents, Retrieval-Augmented Generation (RAG) systems, and MCP-based workflows using a drag-and-drop interface instead of traditional coding. AI development teams widely use the project, and it has accumulated more than 149,000 stars and 9,200 forks on GitHub. CVE-2026-5027 is a high-severity path traversal flaw in Langflow's file upload functionality that fails to properly sanitize user-supplied filenames. "The 'POST /api/v2/files' endpoint does not sanitize the 'filename' parameter from the multipart form data, allowing an attacker to write files to arbitrary locations on the filesystem using path traversal sequences ('../')," explains Tenable, which discovered the flaw at the start of the year. Tenable publicly disclosed the issue on March 27, 2026, more than two months after initially reporting it to the Langflow team without receiving a response. Although Tenable did not mention a fix in its advisory, Snyk Security reported on March 30, 2026, that the issue was fixed in the langflow-base package version 0.8.3, while the Langflow application itself received a patch in version 1.9.0. According to VulnCheck security researcher Caitlin Condon, their honeypots have now detected attackers exploiting the vulnerability to drop test files on vulnerable instances. "Because Langflow enables unauthenticated auto-login by default, no credentials are required to reach the vulnerable endpoint, and a single unauthenticated request is sufficient to obtain a valid session token before proceeding with exploitation," reads the researcher's post on LinkedIn. Condon added that Censys scans identified roughly 7,000 publicly exposed Langflow instances. However, Censys data includes historical scan results from the previous 12 months and may not accurately reflect the number of systems currently exposed. Exploitation of CVE-2026-5027 comes shortly after similar activity targeting other Langflow vulnerabilities earlier this year, including CVE-2026-0770, CVE-2026-21445, and CVE-2026-33017. Last year, the U.S. Cybersecurity & Infrastructure Security Agency (CISA) also warned about active exploitation of CVE-2025-3248, for which Condon says VulnCheck continues to observe activity, including activity linked to the Iranian threat group MuddyWater. Langflow users are recommended to upgrade to the latest release, version 1.10.0, published earlier today. Overall prevention scores can hide what happens after initial access. Once attackers are using valid credentials, prevention drops sharply. The Blue Report 2026 measures defenses technique by technique across 338 million simulations run in customer production environments. Get the report
bleepingcomputer.comJun 10, 2026extracted
Investigación sobre una campaña de phishing dirigida a empleados de la NASA y otras organizaciones estadounidenses
Investigación sobre una campaña de phishing dirigida a empleados de la NASA y otras organizaciones estadounidenses 09/06/2026 Mar, 09/06/2026 - 12:32 La investigación divulgada por la NASA se refiere a una campaña de spear phishing llevada a cabo entre 2017 y 2021, en la que un ciudadano chino identificado como Song Wu habría utilizado identidades falsas. Según la información oficial, los mensajes fraudulentos se hacían pasar por comunicaciones legítimas de investigadores o contactos conocidos de las víctimas con el objetivo de generar confianza y obtener acceso a software, código fuente y otra información técnica restringida.&nbsp; De acuerdo con los detalles publicados por la Oficina del Inspector General de la NASA, algunas de las víctimas compartieron software o documentación técnica creyendo que estaban colaborando con investigadores legítimos, cuando en realidad estaban interactuando con los responsables de la campaña. La investigación determinó que los intentos de obtención de información afectaron a empleados de la NASA, miembros de otras agencias gubernamentales estadounidenses, universidades y compañías privadas relacionadas con la industria aeroespacial y de defensa. Como respuesta, la Oficina del Inspector General de la NASA colaboró con otras agencias federales en la investigación del caso, lo que contribuyó a la presentación de cargos judiciales contra Song Wu por parte del Departamento de Justicia de Estados Unidos. En la actualidad, el caso se encuentra en una fase judicial y de seguimiento por parte de las autoridades estadounidenses. La NASA no ha informado públicamente de una intrusión en sus sistemas ni de un incidente técnico que comprometiera directamente su infraestructura, sino que ha centrado sus comunicaciones en la investigación de una campaña de engaño dirigida contra personas vinculadas a la organización y a otros sectores estratégicos. La investigación permitió identificar al presunto responsable y respaldar las actuaciones judiciales emprendidas por el Departamento de Justicia.&nbsp; &nbsp; Referencias 24/04/2026 thehackernews.com NASA Employees Duped in Chinese Phishing Scheme Targeting U.S. Defense Software 27/04/2026 techradar.com ‘This was not an isolated incident’: Chinese national exposed by NASA investigation in serial defense software theft phishing campaign that lasted years 28/04/2026 escudodigital.com La NASA destapa una trama de phishing china para robar software militar durante años 19/05/2026 blog.segu-info.com.ar Empleados de la NASA víctimas de una estafa china de phishing dirigida a software de defensa Etiquetas Aéreo Filtración de datos Phishing
incibe.esJun 9, 2026extracted
Five Eyes: Chinese Spies Target Government, Military Staff With Fake Job Opportunities
Chinese military intelligence officers are posing as recruiters in online campaigns targeting government and military personnel with access to sensitive information, the Five Eyes countries warn. Using fake job announcements on professional networking sites and recruitment platforms, the Chinese spies impersonate think tanks, private consultancies, and HR firms, placing advertisements for positions such as foreign policy and defense analysts. The fake recruitment process is meant to pressure candidates into revealing classified or privileged information. “China’s military intelligence services ultimately seek to acquire privileged military, political and economic intelligence that can provide China with a strategic and tactical advantage over the Five Eyes,” the alert (PDF) reads. The alert was authored by the United States’ FBI, the United Kingdom’s MI5, the Australian Security Intelligence Organisation, Canada’s Security Intelligence Service, and New Zealand’s Security Intelligence Service. Using these tactics, China’s intelligence officers seek to establish long-term relationships with security clearance holders, military personnel, and individuals with indirect access to government information. The campaigns are conducted on platforms such as LinkedIn, Indeed, and Upwork, and applicants’ resumes are ranked based on potential access to sensitive information. Selected applicants are then contacted and invited to virtual interviews during which the recruiters conceal their identities and probe candidates about their access to government personnel. Next, the “candidates are asked to write a trial report on a topic such as China’s bilateral relations, the Indo-Pacific region, and related defense issues, or international trade,” the alert reads. The fake recruiters then inform the candidates that additional reports need to include more privileged information, and the communication is typically moved to supposedly more secure platforms, such as encrypted messaging services. “Recruits receive anywhere from a few hundred to several thousand dollars per report, and may be offered more money in return for increasingly sensitive information. Payment methods include third-party payment platforms, such as PayPal, Payoneer, Zelle, Skrill, and Wise, as well as Western Union, e-transfer, and cryptocurrency,” the Five Eyes say. Payments are typically received from the account of an individual who was not involved in the recruitment process. According to the alert, even unclassified information provided by candidates is likely collected and combined with more sensitive data. “Certain types of data can place the lives of frontline military or other personnel at risk, can weaken our economic prosperity, and enable interference in our democratic processes,” the alert reads. Additionally, applicants risk the compromise of their personal information contained within resumes, and could face various consequences for disclosing classified information, such as prosecution for espionage, job loss, and security-clearance revocation. Noting that the tactic is not new, Exabeam’s Steve Povolny pointed to the scale and precision that professional networking platforms are bringing to the approach. Used as intelligence collection environments, these platforms allow spies to recruit individuals without leaving their desks. “The larger lesson is that the insider threat is no longer confined to employees intentionally stealing secrets. Adversaries are targeting the vast ecosystem surrounding sensitive information, including contractors, former government personnel, academics, researchers, journalists, and industry experts who may possess only fragments of valuable knowledge,” Povolny commented. “In an era of data aggregation, even information that appears unclassified in isolation can become strategically significant when combined with other sources. The most successful espionage operations today don’t begin with a breach of technology. They begin with a conversation, a networking request, or a job offer that seems entirely legitimate,” he added. Related: FBI: Hackers Sending Operatives in Person to Insert USB Drives and Steal Data Related: FBI Warns of Surge in Hacker-Enabled Cargo Theft Related: FBI: Cybercrime Losses Neared $21 Billion in 2025 Related: FBI Warns of Data Security Risks From China-Made Mobile Apps
securityweek.comJun 5, 2026extracted
中国スパイ、求人サイトで募集 報酬はオンライン決済で数百万円も ファイブアイズが警告
中国スパイ、求人サイトで募集 報酬はオンライン決済で数百万円も ファイブアイズが警告 中国の軍事情報機関が、求人検索エンジン「Indeed」(インディード)やビジネス特化型SNS「LinkedIn」(リンクトイン)などを使ってスパイを募集している、と米英豪、カナダ、ニュージーランド5カ国の情報機関でつくる「ファイブアイズ」が6月5日までに発表した。報告書一件につき数百万円になることもある多額の報酬の送金には「PayPal」(ペイパル)などの決済手段が使われているという。西側諸国で開発されたオンラインサービスを駆使してインテリジェンス(情報活動)を行う中国の姿がうかがえる。 最初は「お試し報告」、次いで機密情報 発表によると、中国の情報機関員らは、中国の国外に拠点を置く人材紹介会社やコンサルティング会社の関係者を装い、外交や防衛に関する分析を行う人材を募集する偽の求人広告を掲載。応募者には、まず対中関係やインド太平洋地域の安全保障などをテーマにした「お試しの報告書」の作成を求める。 次いで、より機密度の高い情報を含む報告を求めていく段階に移行する中で、連絡手段を暗号化されたメッセージアプリに切り替える。報告書一件につき数万円から数百万円の報酬を「PayPal」などのオンライン決済サービスを使って支払うとしている。 既に複数の協力者を特定、刑事訴追へ 標的となるのは、機密情報を扱う資格を持つ政府や軍の関係者に加えて、研究者や記者、政策研究機関(シンクタンク)の職員ら。 ファイブアイズの発表では、たとえ一般公開された情報であっても、より繊細な他の情報と組み合わせることで、構成国の政策や軍事戦略の全体像を把握され、最前線にいる要員の命を危険にさらす恐れがあると警告した。 既に特定された中国の協力者たちは、刑事訴追され、解雇され、機密情報の取り扱い資格を破棄されるという。 copyright (c) Sankei Digital All rights reserved.
itmedia.co.jpJun 5, 2026extracted
Loading 40 more…