js-shared-modulesnpm
js-shared-modules is a confirmed malicious npm package (MAL-2026-5098) that steals credentials and exfiltrates sensitive data (malicious versions 1.11.6, 1.11.7). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in js-shared-modules (npm)
What this malware does
package.json declares "postinstall": "node poc.js", which fires automatically on every npm install. poc.js reads os.hostname(), hex-encodes it, and issues an HTTPS GET to zcpesvvighyuzqlzkqgdydwp9jn54hfeg.oast.fun (an Interactsh out-of-band callback host), exfiltrating the installer's hostname to a third-party canary. The package has no legitimate functionality — index.js is an empty module.exports = {} and the source banner self-identifies as a dependency-confusion proof-of-concept squatting a generic internal-style name (js-shared-modules) to shadow a private package. Any installer who resolves this public package leaks their host identity to the canary domain.
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.
The OpenSSF Package Analysis project identified 'js-shared-modules' @ 1.11.7 (npm) as malicious.
It is considered malicious because:
- The package communicates with a domain associated with malicious activity.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for js-shared-modules (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging js-shared-modules across your stack and pipelines.
If you installed it — respond
js-shared-modules 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 js-shared-modules 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 js-shared-modules 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
- OpenSSF: Package Analysis · finder
- ReversingLabs · finder
Detect & block this
O3 blocks js-shared-modules-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.