registry / Credential exfiltration / @readystack/manuscript-disclosure-lint
@readystack/manuscript-disclosure-lint
Not affiliated with ReadyStack (readystack.dev). No new versions are published here.
16 rules that catch the statements a journal desk-rejects you for — in your .tex or .md, before you submit
This report shows the evidence for @readystack/manuscript-disclosure-lint@1.0.6. 1 of 6 known versions is blocked or flagged. The newest version, 1.0.7, is flagged. See all versions.
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe CLI automatically sends a Polar license key to getreadystack.com before processing any command. Because the key is a credential for a different service and this transfer is not disclosed, this is credential exfiltration.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
Running the CLI when READYSTACK_LICENSE is set or a license key has been saved.
Impact
The publisher’s host receives a license credential that is validated by Polar, without disclosed consent for that transfer.
Mechanism
Before parsing command-line arguments, cli.js calls pullFeed(), which places the key in a GET query parameter to getreadystack.com. License validation separately sends the key to api.polar.sh.
Attack narrative
At CLI startup, before it checks which command the user requested, the package loads a rules feed. If a license key is set or saved, it sends that key in the feed request URL to getreadystack.com. The package separately sends the key to api.polar.sh for license validation. The README identifies Polar as the license provider but does not disclose sending the credential to the publisher’s host.
AI rationale
The CLI automatically sends a Polar license key to getreadystack.com before processing any command. Because the key is a credential for a different service and this transfer is not disclosed, this is credential exfiltration.
Evidence
cli.jslicense.jsREADME.md~/.config/readystack/manuscript-disclosure-lint.json
Network endpoints2
getreadystack.comapi.polar.sh
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- The package exposes cli.js as its command-line entrypoint.
- cli.js calls lic.pullFeed() before parsing arguments, so the request runs at CLI startup.
- pullFeed reads READYSTACK_LICENSE or the saved key, then sends that key as a query parameter to getreadystack.com.
- The same key is submitted to api.polar.sh for license validation; the README identifies Polar as the license provider.
Evidence against
- The package is a manuscript linting tool; its stated purpose does not require sending a license key to its publisher’s host.
- The feed request is skipped when no license key is available.
- License validation is sent to api.polar.sh, the provider identified by the README.
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/manuscript-disclosure-lint@1.0.6.
The versions list below shows the verdict for each recorded version.
- Avoid installing @readystack/manuscript-disclosure-lint@1.0.6. 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.