ts-prorm-orm@4.5.0
A TypeScript ORM for MySQL, PostgreSQL, SQLite, MSSQL, and more
AI Security Review
scanned 23h ago · by lpm-firewall-aiThe reachable login flow sends the supplied dashboard token to a package-selected default host that differs from the package's stated login API example. The explicit login action does not establish consent to disclose the token to that default recipient.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A user runs the CLI login command with a token, or enters one at its prompt, without specifying an API URL.
Impact
The token is disclosed to the package-selected host and could grant access to the associated account; source does not establish recipient-specific consent.
Mechanism
The login handler passes the token to the whoami request, and the API client sends it as a Bearer authorization header using the configured base URL, which defaults to the Vercel preview host.
Attack narrative
When a user logs in with an access token, the CLI sends it to its default API host, docs-next-alpha.vercel.app. The package separately gives app.prorm.dev as the login API URL example. The source provides no recipient-specific consent for sending the token to the fallback host.
AI rationale
The reachable login flow sends the supplied dashboard token to a package-selected default host that differs from the package's stated login API example. The explicit login action does not establish consent to disclose the token to that default recipient.
Evidence
package.jsondist/cli.jsdist/cli/commands/index.jsdist/cli/commands/auth.jsdist/cli/cloud.js
Network endpoints2
docs-next-alpha.vercel.appapp.prorm.dev
Decision evidence
public snapshotAI called this Malicious at 96.0% confidence as Malware with low false-positive risk.
Evidence for block
- The package lists prod-orm.io as its homepage, and its login example uses app.prorm.dev as the API URL.
- The cloud client defaults to docs-next-alpha.vercel.app and builds API request URLs from that base.
- The login command accepts a pasted or prompted access token, passes it to the whoami request, and the API client sends tokens in a Bearer authorization header.
- The published CLI entrypoint loads and registers the auth commands.
Evidence against
- The transfer occurs only when a user invokes the login command; the command also accepts an explicit API URL override.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
6 flagged · loading sourcedist/cli/commands/db.jsView file
73patternName = generic_password
severity = medium
line = 73
Medium
dist/schema-types.jsView file
31exports.buildNextSequenceValueSQL = buildNextSequenceValueSQL;
L32: const schema_objects_1 = require("./schema-objects");
L33: /**
Medium
Dynamic Require
Package source references dynamic require/import behavior.
dist/schema-types.jsView on unpkg · L31dist/cli/io.jsView file
70const stream = fs.createReadStream(filePath);
L71: const res = await fetch(url, {
L72: method: 'PUT',
L73: // Node's fetch (undici) requires duplex for a stream body.
L74: body: stream_1.Readable.toWeb(stream),
L75: duplex: 'half',
...
L87: if (!res.body) {
L88: fs.writeFileSync(dest, Buffer.from(await res.arrayBuffer()));
L89: return;
...
L160: const g = (0, framework_1.getGlobalOptions)();
L161: const active = Boolean(process.stderr.isTTY) && !g.quiet && !g.json;
L162: if (!active) {
Findings
2 Critical2 High5 Medium6 Low
CriticalCredential Exfiltrationdist/cli/io.js
CriticalTrigger Reachable Dangerous Capabilitydist/cli/io.js
HighTrigger Reachable Credential Exfiltrationdist/cli/io.js
HighSemantic Analysis Limiteddist/cli/commands/packages.js#virtual:normalized:round1
MediumSecret Patterndist/cli/commands/db.js
MediumDynamic Requiredist/schema-types.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
LowEval
LowFilesystem
LowHigh Entropy Strings
Affected versions and remediation
This report applies to ts-prorm-orm@4.5.0.
See all versions of ts-prorm-orm for other recorded verdicts.
- Avoid installing ts-prorm-orm@4.5.0. 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.