visanduma/nova-two-factor has 4 versions on Packagist flagged in 1 incident we track. Only the exact versions listed below were named by the source advisories.
visanduma/nova-two-factor is a legitimate package. Only the versions listed were malicious; other versions were not affected, but a lockfile that resolved to a listed version installed the payload.
Affected versions
Check what you actually have installed with composer show visanduma/nova-two-factor.
Socket disclosed on 2026-09-17 that the DPRK-linked PolinRider operators compromised the Visanduma GitHub organisation and implanted staged infostealer code in the dev-main, dev-nova4support, dev-using-inertia, and dev-nova5 branches of visanduma/nova-two-factor, a Laravel Nova 2FA package on Packagist with ~700K cumulative downloads. No stable release is affected; Packagist has frozen the package.
Versions named here: dev-main, dev-nova4support, dev-using-inertia, dev-nova5
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.Rotate every credential that machine or CI job could reach - registry tokens, cloud keys, SSH keys, CI secrets - from a different machine.
2.Pin to a version not listed above, then reinstall from a clean lockfile.
3.Clear caches and private mirrors. Artifactory, Nexus, Verdaccio, and devpi routinely keep serving a tarball after the public registry has pulled it.
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
visanduma/nova-two-factor 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.
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.
