/
← Voltar ao feed

Railway PaaS breach exposes customer environment variables and secrets; crypto wallets drained, Wiz and Symantec report LLMjacking

1 fonte(s) · 1 atualização(ões) · publicado 22/10/2026 08:15 · coletado há 57 minutos

Railway, a Platform-as-a-Service provider, disclosed "anomalous activity" affecting systems that store customer environment variables. An unauthorized third party may have accessed encrypted variables and in some cases obtained the decrypted contents, affecting a "subset of users" (number undisclosed). Railway said the incident is likely part of a series of attacks on platform companies, with the ultimate goal of compromising AI inference providers, and has notified upstream providers so they can proactively revoke exposed keys. Security researcher Taylor Monahan reported that attackers drained cryptocurrency wallets whose private keys were stored on Railway, with the first known theft at 7:36 p.m., at least two hours before official disclosure. The article also covers related LLMjacking activity reported by Wiz and the Symantec Threat Hunter Team.

Detalhes técnicos

  • Exposed data: environment variables such as API keys, database credentials and private registry credentials. Attacker-linked address reported by Monahan: 0xd9773325282874d18cb83f1fe50f14c39750b2ee.
  • Railway rotated all Railway bucket credentials and invalidated Railway API tokens. Builds were restored for Pro and Enterprise workspaces; Hobby, Free and Trial are still being restored, with some builds failing and deployments queued.
  • Wiz documented a related LLMjacking case: sponsored Google Search ads for terms like "google cloud" or "gap" redirected users via Google Sites to a fake Google login page that harvested credentials and MFA codes. Attackers then abused excessive privileges, linked external attacker-controlled GCP projects to the victim's billing accounts and added attacker Gmail accounts to the billing account. AI workloads ran in foreign projects, hiding prompts and outputs from the victim.
  • Symantec reported an offensive AI agent operating in "Skynet mode" that targets exposed LLM endpoints to scan the internet, exploit vulnerabilities, steal credentials, harvest secrets and mine cryptocurrency autonomously for up to 100,000 steps. Targeted deployments include Microsoft Visual Studio Code, Django, Jupyter, Laravel, Supabase, Next.js and Flask/Werkzeug.

Remediação

  • Rotate all environment variables stored in Railway, including API keys, and private registry credentials.
  • Review logs for affected services for unusual activity.
  • Rotate any cryptocurrency wallet private keys that were stored on Railway.

Linha do tempo

  1. thehackernews.com ↗ · pub. 22/10/2026 08:15 · coletado 22/10 09:00 primeiro registro

    Railway PaaS breach exposes customer environment variables and secrets; crypto wallets drained, Wiz and Symantec report LLMjacking

    ler a análise desta fonte

    Railway, a Platform-as-a-Service provider, disclosed "anomalous activity" affecting systems that store customer environment variables. An unauthorized third party may have accessed encrypted variables and in some cases obtained the decrypted contents, affecting a "subset of users" (number undisclosed). Railway said the incident is likely part of a series of attacks on platform companies, with the ultimate goal of compromising AI inference providers, and has notified upstream providers so they can proactively revoke exposed keys. Security researcher Taylor Monahan reported that attackers drained cryptocurrency wallets whose private keys were stored on Railway, with the first known theft at 7:36 p.m., at least two hours before official disclosure. The article also covers related LLMjacking activity reported by Wiz and the Symantec Threat Hunter Team.

    Technical Details

    • Exposed data: environment variables such as API keys, database credentials and private registry credentials. Attacker-linked address reported by Monahan: 0xd9773325282874d18cb83f1fe50f14c39750b2ee.
    • Railway rotated all Railway bucket credentials and invalidated Railway API tokens. Builds were restored for Pro and Enterprise workspaces; Hobby, Free and Trial are still being restored, with some builds failing and deployments queued.
    • Wiz documented a related LLMjacking case: sponsored Google Search ads for terms like "google cloud" or "gap" redirected users via Google Sites to a fake Google login page that harvested credentials and MFA codes. Attackers then abused excessive privileges, linked external attacker-controlled GCP projects to the victim's billing accounts and added attacker Gmail accounts to the billing account. AI workloads ran in foreign projects, hiding prompts and outputs from the victim.
    • Symantec reported an offensive AI agent operating in "Skynet mode" that targets exposed LLM endpoints to scan the internet, exploit vulnerabilities, steal credentials, harvest secrets and mine cryptocurrency autonomously for up to 100,000 steps. Targeted deployments include Microsoft Visual Studio Code, Django, Jupyter, Laravel, Supabase, Next.js and Flask/Werkzeug.

    Remediation

    • Rotate all environment variables stored in Railway, including API keys, and private registry credentials.
    • Review logs for affected services for unusual activity.
    • Rotate any cryptocurrency wallet private keys that were stored on Railway.