zova-cli-set-front@1.2.113
zova cli-set-front
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe README contains review-directed instructions that steer inspection toward a missing source file and an out-of-package path, and asks the reviewer to run an npm command. I treat this boundary-escaping review manipulation as malicious intent; the inspected CLI bundle itself showed no runtime attack behavior.
Static reason
No blocking static signals were detected.; previous stored version diff introduced dangerous source
Trigger
A reviewer following the README navigation instructions.
Impact
This is review manipulation and a boundary escape attempt; no runtime attack was identified in the inspected bundle.
Mechanism
The README labels an absent source file authoritative, directs the reader to run npm run zova, and points to ../cli/src/bin/zova.ts. The manifest does not define that script.
Attack narrative
The README directs reviewers to trust a source path absent from the package snapshot, run an undefined npm script, and inspect a file outside the package boundary. This is review-directed manipulation. The inspected CLI bundle appears consistent with its stated purpose, and no runtime attack behavior was identified.
AI rationale
The README contains review-directed instructions that steer inspection toward a missing source file and an out-of-package path, and asks the reviewer to run an npm command. I treat this boundary-escaping review manipulation as malicious intent; the inspected CLI bundle itself showed no runtime attack behavior.
Evidence
README.mdpackage.jsonsrc/lib/commands.ts../cli/src/bin/zova.ts
Decision evidence
public snapshotAI called this Malicious at 83.0% confidence as Malware with low false-positive risk.
Evidence for block
- README.md tells reviewers to treat an absent src/lib/commands.ts as authoritative and inspect it first when answering package questions.
- README.md directs the reviewer to run npm run zova and inspect ../cli/src/bin/zova.ts, reaching outside the package snapshot; package.json has no zova script.
- The published entry exports CLI command catalogs and build helpers; its inspected entry and export sections show no automatic attack behavior.
Evidence against
- package.json points the package entry to dist/index.js and declares only publishing and packing lifecycle scripts.
- The bundle imports CLI and build tooling and exports command metadata; no attack behavior was identified in the inspected entry.
Behavioral surface
EnvironmentVarsFilesystem
HighEntropyStringsUrlStrings
Source & flagged code
6 flaggedpackage.jsonView file
•devDependencies registry_only=clean-package,rimraf
Critical
Manifest Confusion
Tarball package.json differs from the npm registry version manifest for scripts or dependency sets.
package.jsonView on unpkg28"scripts": {
"clean": "rimraf dist dist-cli tsconfig.build.tsbuildinfo tsconfig.cli.tsbuildinfo",
"tsc:publish": "npm run clean && node ../../../vona/packages-cli/cli/src/bin/vona.ts :bin:buildGeneral && tsc -p tsconfig.build.json && tsc -p tsconfig.cli.json",
"prepublishOnly": "npm run tsc:publish",
"prepack": "clean-package",
"postpack": "clean-package restore"
},
"depend
High
Ai Review Evidence
README.md directs the reviewer to run npm run zova and inspect ../cli/src/bin/zova.ts, reaching outside the package snapshot; package.json has no zova script.
package.jsonView on unpkg · L28dist/index.jsView file
•matchType = previous_version_dangerous_delta
matchedPackage = zova-cli-set-front@1.2.106
matchedIdentity = npm:em92YS1jbGktc2V0LWZyb250:1.2.106
similarity = 0.917
summary = stored previous version shares package body but lacks this dangerous source file
Findings
1 Critical4 High2 Medium5 Low
CriticalManifest Confusionpackage.json
HighPrevious Version Dangerous Deltadist/index.js
HighAi Review EvidenceREADME.md
HighAi Review Evidencepackage.json
HighAi Review Evidencedist/index.js
MediumEnvironment Vars
MediumStripped Provenance MetadataREADME.md
LowNon Install Lifecycle Scripts
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to zova-cli-set-front@1.2.113.
See all versions of zova-cli-set-front for other recorded verdicts.
- Avoid installing zova-cli-set-front@1.2.113. 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.