Skip to main content
Mallory
← Back to News
package-repository-poisoningremote-access-implantcommand-and-control-methodleaked-secret-api-key

Malicious Packagist Packages Masquerading as Laravel Utilities Deploy PHP RAT

Supply Chain Risk · 3 sources · Updated 5mo ago · First seen Mar 4, 2026

Malicious Packagist Packages Masquerading as Laravel Utilities Deploy PHP RAT

Security researchers reported a PHP supply-chain compromise on Packagist in which packages published by the actor nhattuanbl embedded a remote access trojan (RAT) while masquerading as legitimate Laravel utility libraries. The RAT payload was identified in src/helper.php within nhattuanbl/lara-helper and nhattuanbl/simple-queue, while nhattuanbl/lara-swagger acted as a “clean” loader by declaring nhattuanbl/lara-helper as a hard Composer dependency, causing the malicious code to be pulled in during installation.

Once installed, the malware initiates outbound connectivity to the command-and-control endpoint helper[.]leuleu[.]net:2096, sends host profiling/reconnaissance data, and then awaits operator commands, enabling full remote control of the affected host. Reporting indicates the actor used reputation seeding by publishing additional clean packages under the same long-standing Packagist account (created in 2015) during a June–December 2024 publishing window, before releasing the RAT-bearing packages; researchers submitted takedown requests, but the packages were still available at the time of publication. Impacted Laravel/PHP applications may expose sensitive secrets available to the running process (e.g., .env environment variables, database credentials, and API keys).

Does this reach your builds?Trace attribution and downstream blast radius.
Trace the chain
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

6 events · Jun 1, 2024 – Mar 3, 2026
  1. Mar 3, 20269mo ago

    Researchers report C2 is offline but infected hosts remain at risk

    At publication, the command-and-control server was described as non-responsive, but the malware was noted to keep retrying connections indefinitely or at short intervals, meaning previously infected systems could reconnect if infrastructure returns.

  2. Mar 3, 20269mo ago

    Socket submits takedown requests for the malicious packages

    After identifying the malicious packages, Socket submitted takedown requests to Packagist. At the time of reporting, the packages were still available.

  3. Mar 3, 20269mo ago

    Socket identifies the Packagist supply-chain compromise

    Socket's Threat Research Team discovered and analyzed the malicious Packagist packages, linking the activity to the nhattuanbl publisher and documenting the embedded and transitive dependency delivery paths for the RAT.

  4. Dec 1, 20242y ago

    Malicious packages begin deploying a cross-platform PHP RAT

    When installed, the packages automatically execute the payload during Laravel boot or class autoload, launching a background process that profiles the host and connects to helper[.]leuleu[.]net:2096 over AES-128-CTR-encrypted TCP for remote command execution, file operations, and screenshots.

  5. Dec 1, 20242y ago

    Malicious Laravel-themed packages are uploaded to Packagist

    Later in that June–December 2024 publication sequence, the actor published packages including nhattuanbl/lara-helper and nhattuanbl/simple-queue with an obfuscated RAT in src/helper.php, while nhattuanbl/lara-swagger pulled the malware through a hard dependency on lara-helper.

  6. Jun 1, 20242y ago

    Actor publishes Packagist packages under the name nhattuanbl

    A threat actor using the Packagist account name "nhattuanbl" published multiple PHP packages between June and December 2024, including several benign-looking libraries likely intended to build credibility with developers.

Linked entities

Related entities

Vulnerabilities, threat actors, malware, products, organizations, breaches, and observables Mallory has linked to this story. Indicator values are masked here and available in full in the app.

Open in app →

Threat actors

1 linked

Affected products

1 linked
Laravel

Observables

2 linked

Indicator values are masked on this page. See the values in Mallory Domains, IPs, hashes, and URLs are exportable to your SIEM.

Do you run this?See attribution and downstream blast radius, and whether this package or vendor reaches your builds.
Trace the Supply Chain
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.