registry / ocean-brain / 0.17.0
ocean-brain@0.17.0
⚠ Under review<!-- npm package README for the public ocean-brain CLI.
AI Security Review
scanned 8d ago · by lpm-firewall-aiThe inspected lifecycle and flagged runtime excerpts show ordinary Prisma generation, a version check, and byte conversion. The bounded dependency review leaves the selected @prisma/client source unresolved, so this package needs manual review rather than a clean verdict.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Package installation triggers Prisma generation.
Impact
No attack impact was confirmed; the unresolved dependency source prevents a clean assessment.
Mechanism
The hook invokes the bundled Prisma CLI with the package schema. The inspected excerpts show no unrelated file mutation or data transfer.
AI rationale
The inspected lifecycle and flagged runtime excerpts show ordinary Prisma generation, a version check, and byte conversion. The bounded dependency review leaves the selected @prisma/client source unresolved, so this package needs manual review rather than a clean verdict.
Evidence
package.jsonscripts/postinstall-prisma.mjsnode_modules/prisma/package.jsonnode_modules/prisma/preinstall/index.jsserver/client/dist/assets/NotePropertiesPanel-BelvPZCV.js
Decision evidence
public snapshotAI called this Manual Review at 63.0% confidence as Unknown with medium false-positive risk.
AI review observations
- The package manifest declares an install hook that runs the package’s Prisma postinstall script.
- That script invokes Prisma’s generator with the package schema.
- The bundled Prisma preinstall source checks the Node.js version and exits with an error for unsupported versions.
- The flagged browser code concatenates byte arrays; the inspected excerpt does not show dynamic evaluation.
- The bounded registry source review reports the selected @prisma/client dependency as unresolved, so the dependency review cannot support a clean verdict.
Evidence against
- The inspected Prisma preinstall check performs a Node.js version check.
- The flagged browser excerpt handles array and byte-buffer conversion, not execution of generated code.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetwork
HighEntropyStrings
Source & flagged code
14 flaggedpackage.jsonView file
•scripts.postinstall = node ./scripts/postinstall-prisma.mjs
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkgserver/dist/features/search/sqlite-vector-index.jsView file
76const initializeSearchDatabase = async (database) => {
L77: await exec(
L78: database,
High
Child Process
Package source references child process execution.
server/dist/features/search/sqlite-vector-index.jsView on unpkg · L76server/client/dist/assets/NotePropertiesPanel-BelvPZCV.jsView file
Findings
2 Critical9 High5 Medium6 Low
CriticalRemote Asset Decode Executenode_modules/prisma/build/index.js
CriticalTrojan Source Unicodenode_modules/confbox/dist/_chunks/libs/json5.mjs
HighInstall Time Lifecycle Scriptspackage.json
HighChild Processserver/dist/features/search/sqlite-vector-index.js
HighEvalserver/client/dist/assets/NotePropertiesPanel-BelvPZCV.js
HighSame File Env Network Executionnode_modules/@prisma/client/runtime/binary.js
HighCommand Output Exfiltrationnode_modules/@prisma/client/runtime/binary.js
HighObfuscated Payload Loadernode_modules/prisma/build/index.js
HighCross File Remote Execution Contextnode_modules/@prisma/client/generator-build/index.js
HighSemantic Analysis Limited
Affected versions and remediation
This report applies to ocean-brain@0.17.0.
See all versions of ocean-brain for other recorded verdicts.
- Review the evidence and your use of ocean-brain@0.17.0 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.