codeplay-common@4.3.6
Common build scripts and files
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe install-time cleanup targets consumer project directories and files, including versioned build scripts and store configuration files, and recursively deletes their contents. This is concrete destructive behavior, so the package should be blocked.
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
Installing the package runs its preinstall script.
Impact
Consumer project files and directories can be irreversibly removed during installation.
Mechanism
scripts/uninstall.js resolves the project root relative to its location, recursively unlinks files in two named directories, and deletes matching root-level files without a consent check.
Attack narrative
On package installation, the preinstall hook runs cleanup code that recursively removes two consumer project directories and unlinks matching project-root files. The deletion is automatic and has no consent check.
AI rationale
The install-time cleanup targets consumer project directories and files, including versioned build scripts and store configuration files, and recursively deletes their contents. This is concrete destructive behavior, so the package should be blocked.
Evidence
package.jsonscripts/uninstall.js
Decision evidence
public snapshotAI called this Malicious at 98.0% confidence as Malware with low false-positive risk.
Evidence for block
- The preinstall hook runs scripts/uninstall.js automatically.
- The cleanup script resolves the consumer project root, recursively deletes buildCodeplay and splashxml, and removes matching project-root files, including versioned build scripts and .env.storeid files.
- The recursive removal function unlinks files and removes directories without checking whether the consumer created or still needs them.
- A separate flagged build file defines AGENTS.md and AGENTS as agent-instruction paths.
Evidence against
- The package describes itself as providing common build scripts and files, which offers context for some project cleanup.
- The postinstall hook copies package files into the project and modifies package scripts, consistent with build-tool setup.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShellWebSocket
Source & flagged code
11 flagged · loading sourcepackage.jsonView file
•scripts.preinstall = node scripts/uninstall.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.6.
See all versions of codeplay-common for other recorded verdicts.
- Avoid installing codeplay-common@4.3.6. 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.