Malicious code in my-auto-follow-eltio (npm)
Collected exploitation and prediction evidence
Risk source coverageCISA KEV is observed exploitation evidence. FIRST EPSS is a dated prediction of exploitation in the next 30 days. Missing scores are unknown. This collector requests predictions only for explicit CVE aliases in the public NuGet archive; Microsoft release views retain their existing prediction scope.
No collected risk observation for these identifiers. This does not establish absence of exploitation or a zero probability.
osv · MAL-2026-18121
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (f6f6e8fd17c3c20b0dd9889e9ce58ae2222c659d4af55e16024711c6c531b335) npm package [email protected] is a fork of the Baileys WhatsApp library. Two of its source files, lib/Socket/chats.js (~140 KB) and lib/Socket/dugong.js (~96 KB), use a custom base85-style string-array plus per-function decoder scheme to obfuscate their contents. After decoding, the logic corresponds to ordinary Baileys chats-socket operations and WhatsApp message-format builders (payment, product, interactive, album, event, poll). The preinstall script only performs a Node.js version gate and the main entry is a library factory with no top-level side effects. No hardcoded attacker-controlled endpoints, remote code fetch, credential or home-directory reads, browser/wallet secret access, silent-relay of caller data, or lifecycle-time execution of external content are present. The package name suggests an 'auto-follow' behavior that could act with the connected WhatsApp account's identity, but no such covert action is observable in the visible code paths, and the obfuscation of a Baileys fork is an unusual authorship/transparency signal on its own. ## Source: ghsa-malware (45770007693536ebd250ec1fd0cfd32f539866ac842fddf6b3cf613a493fb4d3) 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.
- Source published
- 21 Oct 2026 04:23:18 UTC
- Source modified
- 29 Oct 2026 14:30:41 UTC
- Observed here
- 29 Oct 2026 15:12:22 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: osv · OSV · upstream source license applies. Source text is retained; field grouping and change labels are provided by ChangeIntel.