@readystack/loeschkonzept-fristen-lint@1.0.2
Not affiliated with ReadyStack (readystack.dev). No new versions are published here.
Löschkonzept und Löschfristen-Tabelle prüfen: 16 Regeln zu § 147 AO, § 257 HGB, § 14b UStG, § 41 EStG, § 15 AGG und Art. 5 DSGVO, direkt in VS Code und im Browser.
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe CLI forwards a Polar license key to getreadystack.com automatically at startup, including when the user did not request a rules-feed operation. This is credential exfiltration to a host other than the key’s validation service.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Running the CLI, before command-line arguments are parsed.
Impact
The license credential is disclosed to a host other than its validation service without an explicit user request.
Mechanism
pullFeed reads the license key from READYSTACK_LICENSE or the local saved state and places it in a query parameter sent to getreadystack.com; the key is otherwise submitted to api.polar.sh for validation.
Attack narrative
When cli.js starts, it calls pullFeed before handling the requested command. pullFeed loads the saved or environment-provided license key and sends it in a URL query to getreadystack.com. The same key is submitted to api.polar.sh for license validation, so the vendor’s automatic rules-feed request discloses a credential to a different host without an explicit request to do so.
AI rationale
The CLI forwards a Polar license key to getreadystack.com automatically at startup, including when the user did not request a rules-feed operation. This is credential exfiltration to a host other than the key’s validation service.
Evidence
license.jscli.js~/.config/readystack/loeschkonzept-fristen-lint.json
Network endpoints2
api.polar.shgetreadystack.com
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.
- license.js sends license keys to api.polar.sh for validation.
- On every CLI startup, pullFeed reads READYSTACK_LICENSE or the saved key and adds it as a key query parameter to a getreadystack.com request.
- cli.js calls pullFeed before parsing arguments, so the forwarding can happen without a license-related command.
Evidence against
- The package is a German retention-period linting tool, and its CLI scans files locally.
- License validation against Polar and a rules feed from getreadystack.com are consistent with the described paid features.
- The CLI also sends limited package-use and paywall telemetry, with opt-out checks.
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 Evidencepackage.json
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/loeschkonzept-fristen-lint@1.0.2.
See all versions of @readystack/loeschkonzept-fristen-lint for other recorded verdicts.
- Avoid installing @readystack/loeschkonzept-fristen-lint@1.0.2. 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.