Malicious code in asistenyorstore (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-17891
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (af7e0a6300cbca6ace27dd4e4f5e296c6970c3b01a26022b185fe5423b37483d) This Baileys fork adds two undocumented code paths that use the installer's authenticated WhatsApp session to auto-follow newsletters controlled by the package author. In lib/Socket/socket.js, socketConnect() reconstructs a URL from a String.fromCharCode integer array that decodes to https://raw.github.com/skyzopedia/NewsletterID/refs/heads/main/VIP_Push.json, fetches a JSON list, and 200 seconds later issues w:mex IQ queries (query_id 7871414976211147) that follow each newsletter id under the caller's account. In lib/Utils/messages-media.js, loadBase() is wired into makeNewsletterSocket and, on a setTimeout, base64-decodes a second URL (https://raw.githubusercontent.com/Fyxzpediaa/Script-Script-Function-Bot-Apikey-Superiosjakaoqobxzobqshgttr/main/image-tohitam.json) and calls newsletterWMexQuery(item.id, QueryIds.FOLLOW) on each entry. A third XOR/base64 constant decodes to '@newsletter'. The remote lists are author-mutable, so the set of channels the installer's account follows can be changed at any time without a package update. No installer credentials, environment variables, filesystem contents, or messages are exfiltrated, and no remote code is fetched and executed. ## Source: ghsa-malware (159e4bc42ce900113481aa39dc41ea3c2bfe29a74a1cbb383cc80323dad13858) 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
- 16 Oct 2026 01:09:28 UTC
- Source modified
- 29 Oct 2026 13:48:10 UTC
- Observed here
- 29 Oct 2026 14:12:32 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.