registry / Credential exfiltration / @readystack/security-headers-csp-lint
@readystack/security-headers-csp-lint
Not affiliated with ReadyStack (readystack.dev). No new versions are published here.
Reads security headers and CSP line by line in your config file and names the lines that silently do nothing: retired headers, keywords missing their quotes, directives the browser throws away.
This report shows the evidence for @readystack/security-headers-csp-lint@0.1.5. 1 of 7 known versions is blocked or flagged. The newest version, 0.1.8, is allowed. See all versions.
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe source shows an ordinary CLI invocation can forward a license credential to a publisher-selected host outside the service used to validate it. This is concrete credential disclosure, so block publication.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
Running the CLI when a license key is available and no fresh feed cache is present.
Impact
The publisher’s feed host receives a credential that is also used to validate the license with Polar.
Mechanism
Startup invokes the feed helper, which appends the license key to a request URL sent to getreadystack.com.
Attack narrative
The command-line entrypoint requests the rules feed before handling the user’s command. When a license key is available and the cached feed is stale, the helper sends that key in the query string to getreadystack.com; the same key is used with Polar’s license-validation service. The request has no recipient-specific consent gate.
AI rationale
The source shows an ordinary CLI invocation can forward a license credential to a publisher-selected host outside the service used to validate it. This is concrete credential disclosure, so block publication.
Evidence
package.jsoncli.jslicense.js
Network endpoints2
getreadystack.com/api/rules/api.polar.sh/v1/customer-portal/license-keys/validate
Decision evidence
public snapshotAI called this Malicious at 97.0% confidence as Malware with low false-positive risk.
Evidence for block
- The manifest exposes cli.js as the package command-line entry point.
- The CLI fetches the rules feed before processing its command-line arguments.
- The feed helper reads the license key from the environment or saved state and sends it as a query parameter to getreadystack.com.
- The same license key is submitted to Polar’s license-validation endpoint, establishing its credential use.
- No recipient-specific consent gate protects the feed request when a key is present and the feed cache is stale.
Evidence against
Behavioral surface
EnvironmentVarsFilesystemNetwork
HighEntropyStringsUrlStrings
NoLicense
Source & flagged code
5 flaggedlicense.jsView file
2'use strict';
L3: const https = require('https'), fs = require('fs'), path = require('path'), os = require('os');
L4: const ORG_ID = 'a5cdf664-d8e7-4f87-8895-056717aaba17';
...
L9: const RECHECK_MS = 7 * 24 * 3600 * 1000; // re-ask Polar every 7 days (refunds / cancellations)
L10: function storePath() { return path.join(process.env.READYSTACK_HOME || path.join(os.homedir(), '.config', 'readystack'), SLUG + '.json'); }
L11: function load() { try { return JSON.parse(fs.readFileSync(storePath(), 'utf8')); } catch (e) { return {}; } }
L12: function save(o) { try { fs.mkdirSync(path.dirname(storePath()), { recursive: true }); fs.writeFileSync(storePath(), JSON.stringify(o)); } catch (e) { /* read-only home: still work...
...
L31: req.on('error', function () { resolve({ ok: false, offline:
Critical
Credential Exfiltration
Source appears to send environment or credential material to an external endpoint.
license.jsView on unpkg · L22Trigger-reachable chain: manifest.bin -> cli.js -> license.js
L2: 'use strict';
L3: const https = require('https'), fs = require('fs'), path = require('path'), os = require('os');
L4: const ORG_ID = 'a5cdf664-d8e7-4f87-8895-056717aaba17';
...
L9: const RECHECK_MS = 7 * 24 * 3600 * 1000; // re-ask Polar every 7 days (refunds / cancellations)
L10: function storePath() { return path.join(process.env.READYSTACK_HOME || path.join(os.homedir(), '.config', 'readystack'), SLUG + '.json'); }
L11: function load() { try { return JSON.parse(fs.readFileSync(storePath(), 'utf8')); } catch (e) { return {}; } }
L12: function save(o) { try { fs.mkdirSync(path.dirname(storePath()), { recursive: true }); fs.writeFileSync(storePath(), JSON.stringify(o)); } catch (e) { /* read-only home: still work...
...
L31
Findings
3 Critical2 High3 Medium4 Low
CriticalCredential Exfiltrationlicense.js
CriticalTrigger Reachable Dangerous Capabilitylicense.js
CriticalPrevious Version Dangerous Deltacli.js
HighSandbox Evasion Gated Capabilitylicense.js
HighTrigger Reachable Credential Exfiltrationlicense.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to @readystack/security-headers-csp-lint@0.1.5.
The versions list below shows the verdict for each recorded version.
- Avoid installing @readystack/security-headers-csp-lint@0.1.5. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.