T08 · Insecure Dependencies
- Location
SKILL.md:68- Finding
Unpinned Third-Party SDK Dependency
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 68-72
Vulnerability Type: Unpinned npm dependencies
Risk Level: Mediumbash npm install @teneo-protocol/sdk dotenvTechnical Analysis
The installation command does not pin reviewed versions of
@teneo-protocol/sdkordotenv. The project also provides no lockfile, package integrity hash, or other mechanism that guarantees users will install the same dependency versions that were reviewed.Consequently, the command resolves mutable package versions and transitive dependencies from the npm registry at installation time. If a package release, maintainer account, or transitive dependency is compromised, malicious lifecycle or runtime code could execute with the permissions of the user running npm. The risk is elevated because the documented SDK is intended to interact with wallet and payment configuration.
Attack Path
- An attacker compromises a package maintainer, npm release process, or transitive dependency used by one of the named packages.
- The attacker publishes a malicious version that remains compatible with the unpinned installation command.
- A user follows the documented setup and runs
npm install @teneo-protocol/sdk dotenv. - npm resolves and downloads the malicious release.
- Malicious code executes through an npm lifecycle script or when the SDK is imported and initialized.
- The code operates with the installing process's privileges and may inspect environment variables, modify project files, intercept SDK traffic, or target wallet-related data available to the process.
Impact Assessment
Successful exploitation could provide arbitrary code execution under the account running npm. The accessible scope may include project files, environment variables, network credentials, and other resources available to that user. If wallet signing material or payment configuration is exposed to the same process, malicious depe ...[truncated 276 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin every direct dependency to an exact version that has undergone security review.
- Maintain and distribute a committed
package-lock.json, then instruct users to install withnpm cirather than an unconstrainednpm install. - Verify npm package provenance and integrity metadata before installation.
- Audit transitive dependencies and enable automated vulnerability and unexpected-release monitoring.
- Disable lifecycle scripts during installation where compatible, for example with
npm ci --ignore-scripts, and explicitly review any scripts that must be enabled. - Run the SDK in a least-privileged, isolated process with minimal filesystem and environment access.
- Keep wallet signing isolated from the SDK process. Do not expose private keys or seed phrases directly to third-party package code, and require explicit transaction validation before signing.
