DependencyWatch.io
FeedSolutionsSubmitScan your lockfile
CriticalPackagist0 affected versions

laravel-lang/actions

laravel-lang/actions has 0 versions on Packagist flagged in 1 incident we track. Other versions of this package are not implicated - only the exact versions listed below were named by the source advisories.

Affected versions

Check what you actually have installed with composer show laravel-lang/actions.

    The incident that flagged it

    Critical

    Laravel-Lang Composer packages - every git tag retargeted to a malicious fork commit

    On 2026-05-22 an attacker with push access to the laravel-lang GitHub org retargeted every git tag in laravel-lang/lang, http-statuses, actions, and attributes to malicious fork commits. composer require/update then pulls a src/helpers.php backdoor, autoloaded on every PHP request, that exfiltrates cloud and CI/CD secrets to flipboxstudio.info.

    Versions named here:

    What to do if you installed one of these

    Treat the machine as compromised rather than simply upgrading. Packages in these incidents typically execute at install time, so the payload has already run with whatever credentials were in the environment.

    1. 1.Rotate every credential that machine or CI job could reach - registry tokens, cloud keys, SSH keys, CI secrets - from a different machine.
    2. 2.Pin to a version not listed above, then reinstall from a clean lockfile.
    3. 3.Clear caches and private mirrors. Artifactory, Nexus, Verdaccio, and devpi routinely keep serving a tarball after the public registry has pulled it.
    4. 4.Read the incident write-up above - recommended actions differ per incident, and some have specific indicators of compromise worth grepping your logs for.

    Check your whole project

    laravel-lang/actions is one of many packages in these incidents, and it is usually pulled in as a transitive dependency rather than one you installed directly. We don't parse Packagist manifests yet, but the incident write-ups list every affected package.

    Browse the incident feed All flagged Packagist packages

    Other packages in the same incident

    If laravel-lang/actions is in your tree, these are worth checking too - they were published by the same campaign.

    See the full incident

    Version data comes from the public advisories cited on each incident page. We list only versions those advisories name - we don't infer additional ones. Think this is wrong or incomplete? Tell us.