Malicious Packagist Composer Packages Targeting iOS Devices via Vietnamese Streaming Sites

Technical Analysis

The threat actors published trojanized Composer theme packages to the Packagist registry, exploiting the open-source PHP dependency ecosystem to reach website operators who unknowingly pull these packages into production sites. Once installed, the packages inject malicious JavaScript into the front-end of Vietnamese streaming sites, which then performs client-side fingerprinting to identify visitors on unpatched iOS devices and redirects them into an exploit/spyware delivery chain, alongside a separate ad-fraud and gambling-redirect monetization scheme for other visitors. No specific CVE has been disclosed for the iOS exploitation vector, suggesting reliance on known but unpatched vulnerabilities or social-engineering-based profile/configuration installation prompts rather than a novel zero-day. This is a software supply-chain attack at the package-repository level, similar in mechanism to prior npm/PyPI incidents, and underscores the risk of blindly trusting community-published packages in build pipelines. Organizations running AI coding agents or automated dependency-resolution/CI pipelines that auto-install Composer packages (e.g., agentic DevOps tools performing automated theme/plugin updates) could unknowingly pull these malicious packages into managed web properties, propagating the injected JavaScript and spyware delivery chain into agent-managed infrastructure.

Affected Systems

PHP/Composer-based websites (particularly Vietnamese movie/comic streaming platforms) that installed the 13 identified malicious theme packages from Packagist; end-user unpatched iOS devices visiting affected sites

Indicators of Compromise

• 13 malicious Composer theme packages hosted on Packagist (specific package names not disclosed in source)
• Injected JavaScript payload delivering ad-fraud/gambling redirects
• Secondary payload chain targeting unpatched iOS devices with spyware

Remediation Steps

1. 1

   Audit Composer Dependencies

   Review composer.json and composer.lock files for any of the 13 identified malicious theme packages and remove them immediately.

2. 2

   Package Provenance Verification

   Implement checksum/signature verification and restrict installation to vetted, allow-listed Packagist publishers for theme and plugin packages.

3. 3

   Web Integrity Monitoring

   Deploy subresource integrity checks and content security policy (CSP) headers to detect and block unauthorized injected JavaScript.

4. 4

   iOS Patch Compliance

   Ensure end-user devices and organizational iOS fleets are updated to the latest iOS version to close the vulnerabilities being exploited by the spyware chain.

5. 5

   CI/CD and Agent Pipeline Hardening

   For automated or agent-driven dependency management systems, enforce manual review gates or vulnerability scanning before auto-merging or auto-installing third-party Composer packages.