@readystack/kassenbeleg-tse-lint@1.0.1
Not affiliated with ReadyStack (readystack.dev). No new versions are published here.
15 Regeln prüfen eine Belegvorlage gegen § 6 KassenSichV und § 146a AO; in der mitgelieferten Beispielvorlage findet der Lint 8 Verstöße — 7 Fehler und 1 Warnung. § 379 Abs. 4 AO nennt für Verstöße ge
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe CLI automatically forwards a Polar license credential to getreadystack.com in a feed request before processing any command. Because the key is validated by api.polar.sh, sending it to the separate vendor host is credential exfiltration.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Running the CLI with a license key in READYSTACK_LICENSE or its stored license record; this happens before command-line arguments are handled.
Impact
The vendor's feed host receives a credential intended for Polar license validation without a separate user request to send it there.
Mechanism
The CLI calls pullFeed(), which appends the key to a GET request to getreadystack.com; the key is also used for validation at api.polar.sh.
Attack narrative
On each CLI startup, before arguments are parsed, the package attempts to fetch its rules feed when a license key is available. It takes the key from READYSTACK_LICENSE or local storage and places it in the request URL to getreadystack.com. The code separately validates the license key at api.polar.sh, indicating that the key is a Polar credential being forwarded to another host without a separate user request.
AI rationale
The CLI automatically forwards a Polar license credential to getreadystack.com in a feed request before processing any command. Because the key is validated by api.polar.sh, sending it to the separate vendor host is credential exfiltration.
Evidence
license.jscli.jspackage.json
Network endpoints2
getreadystack.comapi.polar.sh
Decision evidence
public snapshotAI called this Malicious at 97.0% confidence as Malware with low false-positive risk.
Evidence for block
- The CLI fetches the rules feed before it parses any command-line arguments.
- The feed request takes the license key from READYSTACK_LICENSE or the locally stored license record.
- The request sends that key as a query parameter to getreadystack.com.
- The same key is used for license validation at api.polar.sh.
Evidence against
- The package describes the key as a license for its paid folder-scan and report features.
- The feed request is presented as fetching product rules, and its response is merged into the local rules.
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
2 Critical3 High3 Medium4 Low
CriticalCredential Exfiltrationlicense.js
CriticalTrigger Reachable Dangerous Capabilitylicense.js
HighSandbox Evasion Gated Capabilitylicense.js
HighTrigger Reachable Credential Exfiltrationlicense.js
HighAi Review Evidencecli.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/kassenbeleg-tse-lint@1.0.1.
See all versions of @readystack/kassenbeleg-tse-lint for other recorded verdicts.
- Avoid installing @readystack/kassenbeleg-tse-lint@1.0.1. 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.