registry / Credential exfiltration / @readystack/arbeitsvertrag-nachwg-lint
@readystack/arbeitsvertrag-nachwg-lint
Not affiliated with ReadyStack (readystack.dev). No new versions are published here.
Arbeitsvertrag-Vorlagen gegen das Nachweisgesetz prüfen: 15 Pflichtangaben seit 1. August 2022 (§2 NachwG), Auslandseinsatz über vier Wochen (§2 Abs. 2), EU-Entsendung mit Link zur nationalen Website
This report shows the evidence for @readystack/arbeitsvertrag-nachwg-lint@1.0.2. 2 of 3 known versions are blocked or flagged. The newest version, 1.0.3, is flagged. See all versions.
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe CLI automatically sends a Polar-validated license credential to a separate host on startup, without an explicit request to share it with that host. This is credential exfiltration even though the request also fetches a rules feed related to the package.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Running the CLI with a license key in READYSTACK_LICENSE or saved in its local state.
Impact
The license credential is exposed to a host distinct from the Polar validation service, where it may be recorded in request logs or used to access license-linked services.
Mechanism
Startup calls pullFeed, which includes the key as a URL query parameter to getreadystack.com; the key is also sent to api.polar.sh for license validation.
Attack narrative
When the CLI starts, it automatically checks for a saved or environment-provided license key and requests the vendor’s rules feed. That request places the key in the URL query string to getreadystack.com. The source also sends the key to api.polar.sh for validation, indicating that the key is used with a different service. Forwarding this credential to the feed host risks exposing it through that host’s request handling or logs.
AI rationale
The CLI automatically sends a Polar-validated license credential to a separate host on startup, without an explicit request to share it with that host. This is credential exfiltration even though the request also fetches a rules feed related to the package.
Evidence
license.jscli.js~/.config/readystack/arbeitsvertrag-nachwg-lint.json (or the path set by READYSTACK_HOME)
Network endpoints2
getreadystack.com/api/rules/api.polar.sh/v1/customer-portal/license-keys/validate
Decision evidence
public snapshotAI called this Malicious at 89.0% confidence as Malware with low false-positive risk.
Evidence for block
- The published CLI entry point is cli.js.
- On every CLI startup, the program calls pullFeed before processing arguments.
- pullFeed reads the license key from READYSTACK_LICENSE or the local saved state.
- The license key is sent to getreadystack.com in the rules-feed URL query string; the same key is used for validation at api.polar.sh.
Evidence against
- The key is used to fetch the package’s rules feed, a feature related to the linter’s purpose.
- The package has no install lifecycle scripts; the network behavior runs when the CLI is invoked.
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/arbeitsvertrag-nachwg-lint@1.0.2.
The versions list below shows the verdict for each recorded version.
- Avoid installing @readystack/arbeitsvertrag-nachwg-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.