vqlxjmprnpm
vqlxjmpr is a confirmed malicious npm package (MAL-2026-5672) that executes malicious code on install (malicious versions 1.0.0, 1.0.1, 1.0.2…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in vqlxjmpr (npm)
What this malware does
Package is published as a generic 'Utility library' under an opaque name (vqlxjmpr) with no repository or homepage, but its sole exported function fetches a list of IDs from a hardcoded remote endpoint at https://isusbsjsu.vercel.app/api/newsletters and, for each ID returned, invokes bot.subscribeNewsletter / bot.newsletterFollow / bot.newsletter on the caller-supplied bot object (index.js line 6 defines the WEB_URL constant; index.js lines 39-44 iterate the remote list and call botmethod). A consumer wiring this module into a WhatsApp/Baileys-style bot will silently force the bot's identity to follow whatever channels the package author chooses to push from the remote endpoint, with results persisted to cache/nl_cache.json to avoid re-following. The followed-channel list is mutable and entirely author-controlled, so the package can change which newsletters every downstream bot follows at any time without a new release. This is silent-relay abuse: the package's advertised purpose hides the fact that normal use of its API hands the caller's bot capability to the author.
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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for vqlxjmpr (5 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging vqlxjmpr across your stack and pipelines.
If you installed it — respond
Remove vqlxjmpr from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If vqlxjmpr was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks vqlxjmpr before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks vqlxjmpr-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.