registry / @onescience/onecode / 1.14.50-202607021504

@onescience/onecode@1.14.50-202607021504

OneScience AI coding agent for the terminal.

AI Security Review

scanned 3mo ago · by lpm-firewall-ai

Install-time code can fetch an unverified platform binary tarball from a hardcoded IP endpoint with TLS certificate validation disabled. The downloaded payload is extracted and installed as the package CLI binary.

Static reason

One or more suspicious static signals were detected.

Trigger

npm install postinstall lifecycle when platform package is missing

Impact

A remote server can supply executable code that becomes the onecode CLI without registry-published source or integrity protection.

Mechanism

install-time unverified remote binary download and staging

Attack narrative

During npm install, the postinstall script imports platform-bootstrap.mjs and ensures a platform binary exists. If not found locally, it constructs a tgz URL under a hardcoded IP host, downloads it with certificate verification disabled, extracts it with tar, chmods the binary, and links/copies it to bin/.onecode. That stages opaque executable code outside npm registry integrity guarantees.

AI rationale

The source establishes a concrete install-time remote payload path with disabled TLS verification and no integrity check. Even without credential theft or immediate binary execution, this is a blockable staged executable payload carrier.

Evidence

package.jsonpostinstall.mjsplatform-bootstrap.mjsbin/onecodebin/.onecode.platform-version.platform-bootstrap-worknode_modules/onecode-linux-x64.opencode.oneskills

Network endpoints

@onescience/onecode@1.14.50-202607021504

AI Security Review

Decision evidence

Source & flagged code

Source & flagged code

Findings

Affected versions and remediation

Source & flagged code