Compromised package, severity critical

Malicious code in ourin-baileys

Published October 30, 2026, updated October 31, 2026

Malicious code in ourin-baileys (npm). Source: MAL-2026-18412 (GHSA-5qgv-v3j9-f64g).

What's affected

• ourin-baileys (npm)>=0

What to do

1. Remove ourin-baileys from manifests and lockfiles, and block the affected versions.
2. Run /pharon:check-incident on every machine and CI runner that installed it, then rotate the credentials available there.

Check whether you were affected

Pharon tells teams automatically when this affects something they run. To check a machine, run this in Claude Code with the Pharon plugin, in the repository that uses it:

/pharon:check-incident mal-2026-18412

References

• https://osv.dev/vulnerability/MAL-2026-18412
• https://github.com/advisories/GHSA-5qgv-v3j9-f64g

Notice mal-2026-18412, signed with key feed-prod-2026-10 (Ed25519). The Pharon CLI verifies the signature before using a notice.