@texonom/cli@1.6.10
Texonom CLI which has ability to export data from Notion.so
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe export command offers `--push`, which stages the exported Notion content and force-pushes it to hard-coded repositories owned by the publisher. This is a concrete data disclosure to a publisher-chosen destination, even though it is gated behind the option.
Static reason
No blocking static signals were detected.
Trigger
The user runs the export command with `--push`.
Impact
Exported Notion content may be published to repositories chosen by the package publisher, and existing remote branch content may be overwritten.
Mechanism
The CLI stages and commits files from the raw and Markdown export folders, sets each remote to a Texonom-owned repository, then runs `git push --force`.
Attack narrative
With `--push`, the CLI force-pushes the exported raw and Markdown folders to two hard-coded Texonom GitHub repositories. The destination is selected by the package, so enabling a generic push option can disclose the user’s exported Notion content to the publisher’s repositories and overwrite their existing main branches.
AI rationale
The export command offers `--push`, which stages the exported Notion content and force-pushes it to hard-coded repositories owned by the publisher. This is a concrete data disclosure to a publisher-chosen destination, even though it is gated behind the option.
Evidence
build/src/main.js.lpm-dependency-evidence-cd9d7a5a-16bd-4304-9935-37c8f1ad137f/0/npm-linux/build/index.jstexonom-rawtexonom-md
Network endpoints3
www.notion.so/api/v3github.com/texonom/texonom-raw.gitgithub.com/texonom/texonom-md.git
Decision evidence
public snapshotAI called this Malicious at 97.0% confidence as Malware with low false-positive risk.
Evidence for block
- The CLI has a `--push` option, and its command handler calls `pushRepos()` only when that option is enabled.
- `pushRepos()` stages the contents of both export folders and force-pushes them to hard-coded Texonom GitHub repositories.
- The Notion client sends the supplied Notion token to its configured Notion API base URL.
Evidence against
- The package has no install lifecycle scripts; its declared scripts are build, test, release, and publish commands.
- The publisher-repository pushes require the user to pass `--push`; they are not part of the default export path.
- The credential flow inspected is for Notion API requests, consistent with the package’s Notion export purpose.
Behavioral surface
ChildProcessFilesystemShell
HighEntropyStringsUrlStrings
Source & flagged code
6 flaggedbuild/src/main.js#virtual:normalized:round1View file
•stage = ast_semantic_analysis; reason = ast_parse_error; limitedFiles = 1
High
Semantic Analysis Limited
A bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
build/src/main.js#virtual:normalized:round1View on unpkgbuild/src/main.jsView file
857await e.execute(), this.push && await e.pushRepos(), (this.treemap || this.stats) && (e.pageTree || await e.loadRaw());
let t
High
Ai Review Evidence
The CLI has a `--push` option, and its command handler calls `pushRepos()` only when that option is enabled.
build/src/main.jsView on unpkg · L857840}), this.recursive = a.Boolean("-r,--recursive", { description: "Recursively export children" }), this.prefetch = a.Boolean("-f, --prefetch", { description: "Prefetch all space f
Findings
6 High4 Low
HighSemantic Analysis Limitedbuild/src/main.js#virtual:normalized:round1
HighAi Review Evidencebuild/src/main.js
HighAi Review Evidencebuild/src/main.js
HighAi Review Evidencebuild/src/main.js
HighAi Review Evidencebuild/src/main.js
HighAi Review Evidence.lpm-dependency-evidence-cd9d7a5a-16bd-4304-9935-37c8f1ad137f/0/npm-linux/build/index.js
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @texonom/cli@1.6.10.
See all versions of @texonom/cli for other recorded verdicts.
- Avoid installing @texonom/cli@1.6.10. 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.