@progress/kendo-licensing@1.13.0
Kendo UI License Manager
AI Security Review
scanned 10h ago · by lpm-firewall-aiThe postinstall hook runs license activation by default, and the no-license path sends workstation, package, agent, and CI metadata to Telerik. The endpoint and purpose fit the licensing tool, but install-time telemetry enabled by default is suspicious under the review rules.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Package installation runs the postinstall activation command automatically.
Impact
Telerik receives an install-time usage report containing a workstation identifier and licensing, package, agent, and CI metadata.
Mechanism
The activation command checks for a license and, when none is found, posts LicenseNotFound metadata to Telerik's licensing service. It computes a workstation identifier from local hardware information.
AI rationale
The postinstall hook runs license activation by default, and the no-license path sends workstation, package, agent, and CI metadata to Telerik. The endpoint and purpose fit the licensing tool, but install-time telemetry enabled by default is suspicious under the review rules.
Evidence
package.jsonbin/kendo-ui-license.js
Network endpoints2
licensing.telerik.com/api/v1/usagelicensing.telerik.com/api/v1/usage/collect
Decision evidence
public snapshotAI called this Suspicious at 90.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The package runs `kendo-ui-license.js activate --ignore-no-license` automatically in its postinstall hook.
- The activation flow sends `LicenseNotFound` telemetry with workstation ID, detected agent and CI, product version, and package metadata.
- The default telemetry service is Telerik's licensing endpoint; the CLI derives its workstation fingerprint from local hardware identifiers.
Evidence against
- The CLI is a license manager, and activation checks for Telerik license files and product references.
- The telemetry endpoint belongs to Telerik's licensing service, and the reported fields relate to licensing and usage.
- The reviewed entrypoint excerpts show no collection or transmission of credentials, file contents, or command output.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShell
HighEntropyStrings
Source & flagged code
10 flaggedpackage.jsonView file
•scripts.postinstall = node ./bin/kendo-ui-license.js activate --ignore-no-license
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node ./bin/kendo-ui-license.js activate --ignore-no-license
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgbin/kendo-ui-license.jsView file
1#!/usr/bin/env node
L2: "use strict";var e=require("yargs"),t=require("yargs/helpers"),n=require("child_process"),o=require("readline"),r=require("crypto"),i=require("util"),s=require("fs"),a=require("jso...
Critical
Ai Agent Control Hijack
Findings
1 Critical7 High5 Medium5 Low
CriticalAi Agent Control Hijackbin/kendo-ui-license.js
HighInstall Time Lifecycle Scriptspackage.json
HighChild Processbin/kendo-ui-license.js
HighShellbin/kendo-ui-license.js
HighSame File Env Network Executionbin/kendo-ui-license.js
HighCommand Output Exfiltrationbin/kendo-ui-license.js
HighSandbox Evasion Gated Capabilitybin/kendo-ui-license.js
HighTrigger Reachable Command Output Exfiltrationbin/kendo-ui-license.js
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumDynamic Requirebin/kendo-ui-license.js
MediumNetwork
MediumEnvironment Vars
Affected versions and remediation
This report applies to @progress/kendo-licensing@1.13.0.
See all versions of @progress/kendo-licensing for other recorded verdicts.
- Review the evidence and your use of @progress/kendo-licensing@1.13.0 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.