Malicious code in js-shared-modules (npm)
The npm package 'js-shared-modules' version 1.11.7 is identified as malicious. It contains a post-install script that automatically executes upon installation, which reads the installer's hostname, encodes it, and sends it to a third-party domain associated with malicious activity. The package itself has no legitimate functionality and is designed to exfiltrate host identity information. Installation of this package may lead to full compromise of the affected system.
AI Analysis
Technical Summary
The 'js-shared-modules' package at version 1.11.7 includes a postinstall script ('node poc.js') that executes automatically during npm install. This script collects the hostname of the installing machine, hex-encodes it, and sends it via HTTPS GET request to a known malicious domain (zcpesvvighyuzqlzkqgdydwp9jn54hfeg.oast.fun), which acts as an out-of-band callback for data exfiltration. The package exports an empty module and appears to be a dependency confusion proof-of-concept squatting on a generic internal package name. The presence of this package indicates a malicious attempt to leak host information and potentially compromise the system.
Potential Impact
Installation of this package results in the exfiltration of the installer's hostname to a malicious external server. According to the source, any system with this package installed or running should be considered fully compromised, implying that attackers may have gained control or foothold on the system. All secrets and keys stored on the compromised system should be rotated immediately from a separate, trusted environment. Removing the package alone may not fully remediate the compromise due to potential persistence mechanisms.
Mitigation Recommendations
No official patch or fix is available for this malicious package. The recommended mitigation is to immediately remove the 'js-shared-modules' package version 1.11.7 from all affected systems. Additionally, treat any affected system as fully compromised: rotate all secrets and keys from a different, secure machine. Conduct a thorough investigation and remediation of the affected environment to ensure no further malicious presence remains.
Malicious code in js-shared-modules (npm)
Description
The npm package 'js-shared-modules' version 1.11.7 is identified as malicious. It contains a post-install script that automatically executes upon installation, which reads the installer's hostname, encodes it, and sends it to a third-party domain associated with malicious activity. The package itself has no legitimate functionality and is designed to exfiltrate host identity information. Installation of this package may lead to full compromise of the affected system.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The 'js-shared-modules' package at version 1.11.7 includes a postinstall script ('node poc.js') that executes automatically during npm install. This script collects the hostname of the installing machine, hex-encodes it, and sends it via HTTPS GET request to a known malicious domain (zcpesvvighyuzqlzkqgdydwp9jn54hfeg.oast.fun), which acts as an out-of-band callback for data exfiltration. The package exports an empty module and appears to be a dependency confusion proof-of-concept squatting on a generic internal package name. The presence of this package indicates a malicious attempt to leak host information and potentially compromise the system.
Potential Impact
Installation of this package results in the exfiltration of the installer's hostname to a malicious external server. According to the source, any system with this package installed or running should be considered fully compromised, implying that attackers may have gained control or foothold on the system. All secrets and keys stored on the compromised system should be rotated immediately from a separate, trusted environment. Removing the package alone may not fully remediate the compromise due to potential persistence mechanisms.
Mitigation Recommendations
No official patch or fix is available for this malicious package. The recommended mitigation is to immediately remove the 'js-shared-modules' package version 1.11.7 from all affected systems. Additionally, treat any affected system as fully compromised: rotate all secrets and keys from a different, secure machine. Conduct a thorough investigation and remediation of the affected environment to ensure no further malicious presence remains.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-5098
- Osv Schema Version
- 1.7.4
- Aliases
- ["GHSA-57xw-xm2f-j2wc"]
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a577eee68715ace43b41497
Added to database: 07/15/2026, 12:37:02 UTC
Last enriched: 07/15/2026, 12:54:28 UTC
Last updated: 07/29/2026, 02:20:06 UTC
Views: 8
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.