Malicious code in @lynnidoffc/baileys (npm)
What's happening and what to do
Anyone who installed or ran this malicious package should assume an outside attacker has full control of the computer, with access to stored secrets and keys. Removing the package may not remove the malware. npm package @lynnidoffc/baileys, all versions. Rotate all secrets and keys stored on affected computers from a different, clean computer, remove the package, and treat the machine as fully compromised by rebuilding it if possible.
AI summary of the sources on this page. Regenerated when a source changes.
Affected versions
| Ecosystem | Package | Affected | Safe from |
|---|---|---|---|
| npm | @lynnidoffc/baileys | all versions || all versions | None. Remove it. |
Signals over time
- 2026-11-03 22:10First seen here.
- 2026-11-04 09:52Sources last changed.
Source text
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.