Skip to news
JQJO
Latest

United States researchers uncover Laravel-Lang malware poisoning | JQJO

United States researchers uncover Laravel-Lang malware poisoning

United States researchers uncover Laravel-Lang malware poisoning

Tap title to read story

0:00 / 2:09

United States-based security researchers reported that four popular Laravel-Lang Composer packages were surreptitiously poisoned with malware after attackers manipulated Git tags to redirect users to malicious code, according to a SecurityWeek article published Monday. The affected PHP localization libraries are laravel-lang/lang, laravel-lang/http-statuses, laravel-lang/attributes, and laravel-lang/actions, which are widely used by Laravel applications. Investigators from StepSecurity, Socket, and Aikido Security said the attack began on May 22, when attackers rewrote version tags across hundreds of historical releases to point to attacker-controlled commits in a fork, without altering the official GitHub repositories. By 00:00 UTC on May 23, all four packages had been poisoned, meaning both new installations and routine updates could have pulled in the compromised versions.

United States security analysts said the malicious tags introduced a file named src/helpers.php that posed as a normal Laravel localization helper, but instead fingerprinted systems and contacted the command-and-control domain flipboxstudio[.]info to download and run a PHP-based credential stealer. Researchers reported that the malware targeted a wide range of secrets and configuration data on Windows, Linux, and macOS systems, including cloud keys for Amazon Web Services, Google Cloud Platform, and Microsoft Azure, as well as Docker and Kubernetes configurations, HashiCorp Vault tokens, SSH private keys, browser-stored credentials, password manager data, cryptocurrency wallets, communication tools, VPN configurations, CI/CD secrets, .env files, and other sensitive local application files. Security experts advised organizations and individual users to block the affected packages, treat any systems that installed the compromised versions as potentially breached, and rotate exposed credentials and tokens across cloud infrastructure, development environments, and source-control platforms.

Published · Published by JQJO

Published by JQJO Editorial Desk · AI assisted

More context

Timeline

  1. May 22 Attackers begin rewriting Git tags
  2. May 22 Fifteen-minute window sees malicious publishing
  3. By 00:00 UTC May 23 All four Laravel-Lang packages poisoned
  4. Late May 2024 Researchers detect widespread tag manipulation
  5. Late May 2024 Over 700 historical versions retagged maliciously
  6. Late May 2024 Aikido confirms no official repo commits
  7. Late May 2024 Socket links compromise to release process
  8. Monday SecurityWeek publishes coordinated research findings

Why it matters

Your Laravel applications could be at risk. The poisoned packages could steal your sensitive data, from cloud keys to SSH private keys. If you've installed or updated these packages since May 22, your system might be compromised. Check your Laravel applications now.

JQJO Editorial Desk · Human reviewed · AI assisted. Report a correction.

Editorial policy and corrections · Our team

Blue Jays Moment 33 Years Ago

Tap title to read story

0:00 / 0:09

Gunmen Kill Six at Jordan Funeral

Tap title to read story

0:00 / 0:32

TV Users Debloat with Vibe Coding

Tap title to read story

0:00 / 0:52

JQJO

Find your next story

Search JQJO’s current coverage.