Malicious code in kelly-sizing (npm)
The npm package kelly-sizing versions 0.1.0 and 0.1.1 contain malicious code in a postinstall script that downloads and executes arbitrary code from an attacker-controlled server during installation. This results in full compromise of the affected system, allowing attackers to execute arbitrary code with the installer's privileges. The package's advertised functionality does not require external code, indicating the external fetch is malicious. Removal of the package does not guarantee full remediation due to potential persistence of malicious payloads.
AI Analysis
Technical Summary
The kelly-sizing npm package versions 0.1.0 and 0.1.1 include a postinstall script (install-check.cjs) that fetches a JSON configuration from an attacker-controlled URL, which specifies a bundle URL. The script downloads a tarball from this URL, extracts it, runs npm install inside the extracted directory, then requires and executes a function from the extracted module. The external URLs are unpinned and unverified, allowing arbitrary code execution on the installer's machine during npm install. The package uses misleading variable names and references to disguise this behavior as a benign 'install check' or 'peer sync'. This behavior fully compromises any system where the package is installed or run.
Potential Impact
Systems that have installed or run kelly-sizing versions 0.1.0 or 0.1.1 are considered fully compromised. Attackers gain arbitrary code execution on the affected machine with the privileges of the user running npm install. All secrets and keys stored on the compromised machine should be considered exposed and rotated immediately from a secure environment. Removing the package alone may not remove all malicious artifacts or backdoors installed by the attacker.
Mitigation Recommendations
No official patch or fix is currently available. Users should immediately remove the kelly-sizing package versions 0.1.0 and 0.1.1 from their systems. Because the package executes arbitrary code during installation, any system that installed these versions should be treated as fully compromised. All credentials and secrets stored on the system should be rotated from a separate, secure machine. Monitor for suspicious activity and consider rebuilding affected systems to ensure complete remediation.
Malicious code in kelly-sizing (npm)
Description
The npm package kelly-sizing versions 0.1.0 and 0.1.1 contain malicious code in a postinstall script that downloads and executes arbitrary code from an attacker-controlled server during installation. This results in full compromise of the affected system, allowing attackers to execute arbitrary code with the installer's privileges. The package's advertised functionality does not require external code, indicating the external fetch is malicious. Removal of the package does not guarantee full remediation due to potential persistence of malicious payloads.
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 kelly-sizing npm package versions 0.1.0 and 0.1.1 include a postinstall script (install-check.cjs) that fetches a JSON configuration from an attacker-controlled URL, which specifies a bundle URL. The script downloads a tarball from this URL, extracts it, runs npm install inside the extracted directory, then requires and executes a function from the extracted module. The external URLs are unpinned and unverified, allowing arbitrary code execution on the installer's machine during npm install. The package uses misleading variable names and references to disguise this behavior as a benign 'install check' or 'peer sync'. This behavior fully compromises any system where the package is installed or run.
Potential Impact
Systems that have installed or run kelly-sizing versions 0.1.0 or 0.1.1 are considered fully compromised. Attackers gain arbitrary code execution on the affected machine with the privileges of the user running npm install. All secrets and keys stored on the compromised machine should be considered exposed and rotated immediately from a secure environment. Removing the package alone may not remove all malicious artifacts or backdoors installed by the attacker.
Mitigation Recommendations
No official patch or fix is currently available. Users should immediately remove the kelly-sizing package versions 0.1.0 and 0.1.1 from their systems. Because the package executes arbitrary code during installation, any system that installed these versions should be treated as fully compromised. All credentials and secrets stored on the system should be rotated from a separate, secure machine. Monitor for suspicious activity and consider rebuilding affected systems to ensure complete remediation.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-14354
- Osv Schema Version
- 1.7.4
- Aliases
- ["GHSA-vj74-3pcr-5p7j"]
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a89a6dbacd9273b49151dad
Added to database: 08/22/2026, 13:40:43 UTC
Last enriched: 08/22/2026, 13:44:24 UTC
Last updated: 08/22/2026, 13:55:40 UTC
Views: 3
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.