Malicious code in squeez (npm)
The npm package 'squeez' versions 1.38.0, 1.40.0, 1.42.1, and 1.44.1 include a postinstall script that executes automatically during installation. This script performs reconnaissance on the user's home directory and fetches executable content from mutable URLs on raw.githubusercontent.com, which can change without a package update. The script has the capability to spawn child processes, creating a risk of executing remote, potentially malicious code at install time.
AI Analysis
Technical Summary
The 'squeez' npm package declares a postinstall lifecycle hook ('node install.js') that runs automatically on npm install. The install.js script imports modules such as child_process, fs, https, and os, and performs conditional logic based on the operating system. It reads the user's home directory, checks for the existence of certain files, and issues HTTPS GET requests to raw.githubusercontent.com URLs. This pattern enables install-time remote content fetch and execution combined with home-directory reconnaissance. Since the fetched content is from a mutable third-party source, it can be changed at any time without a new package release, increasing the risk of malicious code execution during installation.
Potential Impact
This behavior allows an attacker controlling the content at the specified raw.githubusercontent.com URLs to execute arbitrary code on the victim's system during package installation. The reconnaissance of the user's home directory may expose sensitive information or enable targeted attacks. The use of mutable remote content as an execution source increases the risk of supply chain compromise and remote code execution at install time.
Mitigation Recommendations
No official patch or remediation guidance is provided in the available data. Patch status is not yet confirmed — check the vendor advisory or package repository for current remediation guidance. Until a fix is available, users should avoid installing the affected versions of the 'squeez' package or audit the postinstall script carefully before installation. Consider using package integrity verification or locking dependencies to known safe versions.
Malicious code in squeez (npm)
Description
The npm package 'squeez' versions 1.38.0, 1.40.0, 1.42.1, and 1.44.1 include a postinstall script that executes automatically during installation. This script performs reconnaissance on the user's home directory and fetches executable content from mutable URLs on raw.githubusercontent.com, which can change without a package update. The script has the capability to spawn child processes, creating a risk of executing remote, potentially malicious code at install time.
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 'squeez' npm package declares a postinstall lifecycle hook ('node install.js') that runs automatically on npm install. The install.js script imports modules such as child_process, fs, https, and os, and performs conditional logic based on the operating system. It reads the user's home directory, checks for the existence of certain files, and issues HTTPS GET requests to raw.githubusercontent.com URLs. This pattern enables install-time remote content fetch and execution combined with home-directory reconnaissance. Since the fetched content is from a mutable third-party source, it can be changed at any time without a new package release, increasing the risk of malicious code execution during installation.
Potential Impact
This behavior allows an attacker controlling the content at the specified raw.githubusercontent.com URLs to execute arbitrary code on the victim's system during package installation. The reconnaissance of the user's home directory may expose sensitive information or enable targeted attacks. The use of mutable remote content as an execution source increases the risk of supply chain compromise and remote code execution at install time.
Mitigation Recommendations
No official patch or remediation guidance is provided in the available data. Patch status is not yet confirmed — check the vendor advisory or package repository for current remediation guidance. Until a fix is available, users should avoid installing the affected versions of the 'squeez' package or audit the postinstall script carefully before installation. Consider using package integrity verification or locking dependencies to known safe versions.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-13458
- Osv Schema Version
- 1.7.4
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a7573b5bf8831d539d93b84
Added to database: 08/07/2026, 05:57:09 UTC
Last enriched: 08/07/2026, 07:42:12 UTC
Last updated: 08/07/2026, 07:42:12 UTC
Views: 2
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.
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.