merchantweb-lang-cookie-resetnpm
merchantweb-lang-cookie-reset is a confirmed malicious npm package (MAL-2026-13449) that executes malicious code on install (malicious versions 0.0.6, 0.0.999, 0.1.0…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in merchantweb-lang-cookie-reset (npm)
What this malware does
package.json declares the sole dependency packet-table-thread-stream as a direct tarball URL to a non-npm host (https://artifacts.yosiroute.com/npm/packet-table-thread-stream), with no version pin and no integrity hash. The shrinkwrap marks that dependency hasInstallScript: true, so on npm install npm fetches opaque code from artifacts.yosiroute.com and executes its lifecycle scripts on the installer's machine, bypassing npm registry scanning. The wrapper package itself is a disposable shim: index.js is trivial (only re-exports name/version), and package.json metadata is placeholder (author: Package Registry, description: Generated package, repo: github.com/example/...). The package's only functional effect on install is pulling attacker-controlled code from a non-registry host into the installer's dependency tree and running its install scripts.
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 merchantweb-lang-cookie-reset (10 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging merchantweb-lang-cookie-reset across your stack and pipelines.
If you installed it — respond
Remove merchantweb-lang-cookie-reset 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 merchantweb-lang-cookie-reset 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 merchantweb-lang-cookie-reset 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 merchantweb-lang-cookie-reset-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.