codeplay-common@4.3.1
Common build scripts and files
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe install hook configures the consumer build to run a script that can update project-level agent instructions from a publisher-controlled endpoint. Because this behavior is build-triggered and the source does not establish harmful content, it warrants a warning rather than a block.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review; previous stored version diff introduced dangerous source
Trigger
The consumer runs the build command configured by the package’s postinstall script.
Impact
The downloaded instructions may influence AI agents working in the consumer project; the inspected source does not establish what those instructions contain.
Mechanism
The build script fetches a versioned ZIP from htmlcodeplay.com, validates archive paths, then copies its AGENTS.md and AGENTS/ contents into the project root, overwriting existing files.
AI rationale
The install hook configures the consumer build to run a script that can update project-level agent instructions from a publisher-controlled endpoint. Because this behavior is build-triggered and the source does not establish harmful content, it warrants a warning rather than a block.
Evidence
package.jsonscripts/sync-files.jsfiles/buildCodeplay/codeplayBeforeBuild-6.2.jsAGENTS.mdAGENTS/
Network endpoints1
htmlcodeplay.com/code-play-plugin/
Decision evidence
public snapshotAI called this Suspicious at 84.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- package.json runs scripts/sync-files.js during postinstall; that script sets the consumer build command to run codeplayBeforeBuild.
- The build script fetches a versioned archive from htmlcodeplay.com and copies its AGENTS.md and AGENTS/ contents into the project root, replacing existing files.
- The build script calls the agent-instructions updater automatically during its build sequence; source does not show a recipient-specific consent check for that update.
Evidence against
- The agent-instructions update is reached through the configured build command, not directly from the package’s install hooks.
- The archive validator rejects absolute paths and entries containing .. before extraction.
Behavioral surface
ChildProcessDynamicRequireEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
9 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node scripts/sync-files.js
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkgfiles/buildCodeplay/apk-store-builder.jsView file
1const { spawn } = require("child_process");
L2: const path = require("path");
High
Child Process
Package source references child process execution.
files/buildCodeplay/apk-store-builder.jsView on unpkg · L1scripts/sync-files.jsView file
1const fs = require("fs");
L2: const path = require("path");
Medium
Findings
1 Critical8 High4 Medium4 Low
CriticalPrevious Version Dangerous Deltafiles/buildCodeplay/codeplayBeforeBuild-6.2.js
HighInstall Time Lifecycle Scriptspackage.json
HighChild Processfiles/buildCodeplay/apk-store-builder.js
HighShell
HighRuntime Package Installfiles/buildCodeplay/codeplayBeforeBuild-6.2.js
HighSemantic Analysis Limitedfiles/buildCodeplay/codeplayBeforeBuild-6.2.js
HighKnown Malware Source Similarityfiles/iap-install-2.js
HighKnown Malware Source Similarityfiles/buildCodeplay/manifestModification.js
HighKnown Malware Source Similarityfiles/scripts/setup-baseline-profile.js
MediumDynamic Requirescripts/sync-files.js
MediumNetwork
Affected versions and remediation
This report applies to codeplay-common@4.3.1.
See all versions of codeplay-common for other recorded verdicts.
- Review the evidence and your use of codeplay-common@4.3.1 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.