codeplay-common@4.3.7
Common build scripts and files
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe package introduces an automatic remote update path for project agent instructions during builds, leaving a concrete configuration risk. The inspected source does not prove malicious content or behavior, so this 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
Running the project build command installed or updated by the package’s postinstall sync.
Impact
Downloaded instructions can change guidance read by AI agents working in the project; no specific harmful instruction or resulting action is established by the inspected source.
Mechanism
The build script fetches a versioned archive from the package publisher’s host, then copies its AGENTS.md and directory contents into the project, overwriting existing directory files.
AI rationale
The package introduces an automatic remote update path for project agent instructions during builds, leaving a concrete configuration risk. The inspected source does not prove malicious content or behavior, so this 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 87.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The manifest runs a postinstall file sync and a preinstall cleanup script.
- The postinstall sync adds a build command that runs the package’s build script when a project build is invoked.
- That build script fetches version information and can replace AGENTS.md and recursively overwrite the project’s AGENTS directory with downloaded content.
- The build script runs this agent-instruction update as part of its main routine.
- The ZIP path check rejects absolute paths and parent-directory traversal.
Evidence against
- The agent-instruction update is reached through the project build command, not directly through the package lifecycle hook.
- The update targets first-party agent-instruction paths and checks archive paths before extraction; the inspected source does not establish malicious downloaded content.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShellWebSocket
Source & flagged code
11 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/generate-ai-promo-video.jsView file
7const { createHash } = require('node:crypto');
L8: const { spawnSync } = require('node:child_process');
L9:
High
Child Process
Package source references child process execution.
files/generate-ai-promo-video.jsView on unpkg · L7scripts/sync-files.jsView file
1const fs = require("fs");
L2: const path = require("path");
Medium
Findings
1 Critical10 High4 Medium4 Low
CriticalPrevious Version Dangerous Deltafiles/buildCodeplay/codeplayBeforeBuild-6.2.js
HighInstall Time Lifecycle Scriptspackage.json
HighChild Processfiles/generate-ai-promo-video.js
HighShell
HighSame File Env Network Executionfiles/generate-ai-promo-video.js#virtual:normalized:round1
HighCommand Output Exfiltrationfiles/generate-ai-promo-video.js#virtual:normalized:round1
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
Affected versions and remediation
This report applies to codeplay-common@4.3.7.
See all versions of codeplay-common for other recorded verdicts.
- Review the evidence and your use of codeplay-common@4.3.7 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.