# ophimcms/theme-pcc - compromised Packagist versions

> ophimcms/theme-pcc on Packagist has 1 version flagged in 1 tracked supply-chain incident. Only the exact versions listed below were named by the source advisories. ophimcms/theme-pcc was malicious from its first publish. There is no legitimate version to roll back to; remove it entirely.

- Package: ophimcms/theme-pcc
- Ecosystem: Packagist
- Highest severity: medium
- Kind: Malicious package
- Compromised versions: 1.2.2
- Check what you have installed: `composer show ophimcms/theme-pcc`

## The incident that flagged it

| Date | Severity | Kind | Incident | Versions named |
|---|---|---|---|---|
| 2026-03-12 | medium | Malicious package | [6 malicious Packagist OphimCMS themes ship trojanised jQuery and FUNNULL redirects](https://dependencywatch.io/incident/packagist-2026-03-12-ophimcms-themes) | 1.2.2 |

## What to do if you installed one of these

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

## Check your whole project

We don't parse Packagist manifests yet, but the incident write-ups list every affected package. Incident feed: https://dependencywatch.io/feed

All flagged Packagist packages: https://dependencywatch.io/package/packagist

## Other packages in the same incident

If ophimcms/theme-pcc is in your tree, these are worth checking too - they were published by the same campaign.

- [ophimcms/theme-dy](https://dependencywatch.io/package/packagist/ophimcms/theme-dy) (Packagist)
- [ophimcms/theme-legend](https://dependencywatch.io/package/packagist/ophimcms/theme-legend) (Packagist)
- [ophimcms/theme-motchill](https://dependencywatch.io/package/packagist/ophimcms/theme-motchill) (Packagist)
- [ophimcms/theme-mtyy](https://dependencywatch.io/package/packagist/ophimcms/theme-mtyy) (Packagist)
- [ophimcms/theme-rrdyw](https://dependencywatch.io/package/packagist/ophimcms/theme-rrdyw) (Packagist)

Full incident: https://dependencywatch.io/incident/packagist-2026-03-12-ophimcms-themes

## Sourcing

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. Corrections: https://dependencywatch.io/submit

---

Canonical page: https://dependencywatch.io/package/packagist/ophimcms/theme-pcc
Markdown version: https://dependencywatch.io/package/packagist/ophimcms/theme-pcc.md
Site index for agents: https://dependencywatch.io/llms.txt
DependencyWatch.io is operated by Precursor Security (https://precursorsecurity.com).