Back to skill

Security audit

Sinopec Oil Price

Security checks for vulnerabilities and agentic risk

Overview

This appears to be a legitimate Sinopec oil-price lookup and monitoring skill, with dependency hardening issues but no evidence of hidden exfiltration, destructive behavior, or automatic persistence.

Before installing, treat this as a China-focused Sinopec oil-price tool that may create local history files if monitoring is used. Prefer regenerating the lockfile from a trusted registry, updating the reported vulnerable dependencies, and only enabling the cron example if you explicitly want recurring monitoring.

Vulnerability Patterns
  • Insecure DependenciesIntroduces malicious components through unsafe dependency sources
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
Findings (1)

T08 · Insecure Dependencies

Warning
Location
package-lock.json:21
Finding

Dependencies Are Retrieved from a Third-Party npm Registry Mirror

Content
View full analysis

Vulnerability Details

File Location: package-lock.json:21-31
Vulnerability Type: Third-party dependency source trust
Risk Level: Medium

json
"node_modules/axios": {
  "version": "1.13.6",
  "resolved": "https://registry.npmmirror.com/axios/-/axios-1.13.6.tgz",
  "integrity": "sha512-ChTCHMouEe2kn713WHbQGcuYrr6fXTBiu460OTwWrWob16g1bXn4vtz07Ope7ewMozJAnEquLk5lWQWtBig9DQ==",
  "license": "MIT",
  "dependencies": {
    "follow-redirects": "^1.15.11",
    "form-data": "^4.0.5",
    "proxy-from-env": "^1.1.0"
  }
}

Technical Analysis

The lockfile resolves axios and its transitive dependencies through registry.npmmirror.com, a third-party npm registry mirror, rather than the official registry.npmjs.org registry. This adds another trust boundary to the dependency installation process.

The recorded SHA-512 integrity values provide meaningful protection against an artifact being changed without a corresponding lockfile update. However, they do not eliminate risks arising from a compromised mirror and lockfile-generation workflow, a malicious artifact already represented by the lockfile, or differences in package provenance and availability.

The audit found no evidence that the currently locked packages are malicious, and no dependency lifecycle scripts were identified in the supplied lockfile. The issue is therefore a supply-chain hardening concern rather than proof of active compromise.

Attack Path

  1. An attacker compromises the configured third-party registry mirror, its upstream synchronization process, or the environment used to generate the lockfile.
  2. A malicious or substituted dependency artifact is selected and a matching lockfile integrity value is introduced, or installation occurs without enforcing the reviewed lockfile.
  3. A developer or deployment system installs dependencies from the mirror.
  4. Malicious dependency code executes through an installation lifecycle ...[truncated 822 chars]
Remediation
View remediation

Remediation Suggestions

  1. Configure npm to use the official registry:
    bash
    npm config set registry https://registry.npmjs.org/
    
  2. Remove and regenerate the lockfile in a controlled environment:
    bash
    rm -rf node_modules package-lock.json
    npm install
    
  3. Review the regenerated dependency versions and integrity hashes before committing the lockfile.
  4. Use npm ci in CI and production so installation strictly follows the reviewed lockfile.
  5. Prevent registry overrides through unreviewed project, user, or CI .npmrc files.
  6. Run dependency vulnerability and provenance checks during CI, such as npm audit, software composition analysis, and package-signature or provenance verification where supported.
  7. Restrict installation and runtime environments through non-root execution, minimal filesystem access, limited environment secrets, and outbound network controls.
  8. Consider pinning the direct dependency to an exact reviewed version instead of the broad ^1.6.0 range used in package.json.
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Findings (16)

Tp4

High
Category
MCP Tool Poisoning
Confidence
94% confidence
Finding

声明描述的是一个查询型技能:按省份获取实时油价并展示价格变动信息。实际代码虽然确实调用了油价查询能力,但其主要功能已扩展为“监控/通知”脚本:它固定查询广西,不体现通用的按省份查询;会读取并保存历史价格到本地文件;并生成用于自动通知的消息内容,明确面向 cron 或消息系统集成。这些属于未声明的重要能力和不同的主要用途,因此描述与代码行为存在实质性不匹配。

Content

No source excerpt is available for this finding.

Ae1

High
Category
analysis-evasion
Confidence
100% confidence
Finding

Referenced artifact was not completely inspected

Content

Scanner excerpt · SKILL.md (reported line 58)May include surrounding context.

md
- **[Usage Examples](references/examples.md)** - Code patterns and common scenarios

Known Vulnerable Dependency: axios==1.13.6 — 16 advisory(ies): CVE-2026-44494 (axios Vulnerable to Full Man-in-the-Middle via Prototype Pollution Gadget in `co); CVE-2026-44495 (axios Vulnerable to Credential Theft and Response Hijacking via Prototype Pollut); CVE-2025-62718 (Axios has a NO_PROXY Hostname Normalization Bypass that Leads to SSRF) +13 more

High
Category
Supply Chain
Confidence
93% confidence
Finding

The lockfile pins axios 1.13.6, which is reported by the scanner as having multiple advisories including SSRF-related proxy bypass and prototype-pollution-assisted MITM/credential theft issues. This skill’s purpose is to query external real-time oil price data, so its core behavior depends on outbound HTTP requests; if vulnerable axios behavior is reachable, network-originated attacks can affect confidentiality and request integrity.

Content

No source excerpt is available for this finding.

Known Vulnerable Dependency: form-data==4.0.5 — 1 advisory(ies): CVE-2026-12143 (form-data: CRLF injection in form-data via unescaped multipart field names and f)

High
Category
Supply Chain
Confidence
80% confidence
Finding

form-data 4.0.5 is flagged for CRLF injection via unescaped multipart field names and filenames, but this skill’s described function is only oil price lookup, not file upload or multipart form submission. The dependency is present transitively through axios, so the issue is real in the dependency tree but likely has limited exploitability in this specific skill unless multipart requests are constructed from untrusted input.

Content

No source excerpt is available for this finding.

Known Vulnerable Dependency: axios==1.13.6 — 16 advisory(ies): CVE-2026-44494 (axios Vulnerable to Full Man-in-the-Middle via Prototype Pollution Gadget in `co); CVE-2026-44495 (axios Vulnerable to Credential Theft and Response Hijacking via Prototype Pollut); CVE-2025-62718 (Axios has a NO_PROXY Hostname Normalization Bypass that Leads to SSRF) +13 more

High
Category
Supply Chain
Confidence
88% confidence
Finding

The skill depends on axios, and the analysis reports that the resolved version is affected by multiple published advisories, including SSRF/proxy-bypass and prototype-pollution-related man-in-the-middle and credential-theft risks. Because this skill queries remote oil-price data, it necessarily performs outbound HTTP requests, which makes flaws in the HTTP client materially relevant rather than theoretical.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

This codebase presents its skill description and all user-facing status/error text in Chinese, with no indication that users can choose another language or locale. The audit criteria flag language/locale constraints when a skill forces a specific language without opt-in.

Content

No source excerpt is available for this finding.

Description-Behavior Mismatch

Medium
Category
Not specified by scanner
Confidence
93% confidence
Finding

The manifest describes a query skill for retrieving current oil prices and showing price change information, which implies presenting change data returned by the upstream source. Here the code adds a broader monitoring feature that tracks prior runs by reading and writing local history files, then generates change notifications based on persisted state.

Content

No source excerpt is available for this finding.

Context-Inappropriate Capability

Medium
Category
Not specified by scanner
Confidence
89% confidence
Finding

The skill persists user-influenced data to local files using the province name directly in the filename. Even though the expected use is province labels, there is no validation or allowlist, so a crafted province value could cause path traversal or unintended file writes if this method is invoked with arbitrary input in the host environment.

Content

No source excerpt is available for this finding.

Description-Behavior Mismatch

Medium
Category
Not specified by scanner
Confidence
92% confidence
Finding

The manifest describes a skill for querying real-time oil price information by province and showing price changes. This file implements additional stateful monitoring behavior by reading and writing a local history file, turning the skill into a persistent tracker rather than just a query utility.

Content

No source excerpt is available for this finding.

Description-Behavior Mismatch

Medium
Category
Not specified by scanner
Confidence
90% confidence
Finding

The manifest says the skill supports querying gasoline and diesel prices by province. Here, the operational behavior is fixed to province_name: '广西', so this file does not actually expose the broader province-querying behavior implied by the description.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
92% confidence
Finding

This is a markdown file, so SQP-2 applies to omissions in the skill description about behaviors affecting privacy or user data. The API docs state that monitorOilPrice accepts a recipient_id as a user's open_id for notifications, but do not include any warning or disclosure that the skill may send notifications or process user identifiers.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
91% confidence
Finding

The primary description is written entirely in Chinese, and the tool metadata also uses Chinese-only descriptions. This can constitute a language/locale policy issue because the skill does not indicate that language is user-selectable or that the Chinese-only constraint is intentional for a region-specific audience.

Content

No source excerpt is available for this finding.

Known Vulnerable Dependency: follow-redirects==1.15.11 — 1 advisory(ies): CVE-2026-40895 (follow-redirects leaks Custom Authentication Headers to Cross-Domain Redirect Ta)

Low
Category
Supply Chain
Confidence
81% confidence
Finding

follow-redirects 1.15.11 is flagged for leaking custom authentication headers across cross-domain redirects. Because axios depends on this library and the skill makes HTTP requests to retrieve pricing data, a malicious or compromised upstream endpoint could potentially redirect requests and expose sensitive headers if any are configured.

Content

No source excerpt is available for this finding.

Unpinned Dependencies

Low
Category
Supply Chain
Confidence
95% confidence
Finding

The dependency uses a caret range (^1.6.0) instead of an exact pinned version, which permits installation of newer axios releases without explicit review. In a security-sensitive skill, this weakens supply-chain control and can unintentionally pull in vulnerable or behavior-changing versions, as reflected by the separate vulnerable-dependency finding.

Content

Scanner excerpt · package.json (reported line 11)May include surrounding context.

json
"monitor": "node monitor-oil-price.js"
  },
  "dependencies": {
    "axios": "^1.6.0"
  },
  "keywords": ["openclaw", "skill", "oil-price", "sinopec"],
  "author": "",

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
81% confidence
Finding

SQP-3 applies to natural-language policy issues in all file types, including markdown. The file presents the skill documentation entirely in Chinese and does not indicate that language selection is optional or that the skill is intentionally limited to a Chinese-speaking audience.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
83% confidence
Finding

The file’s headings, examples, comments, and output strings are entirely in Chinese, including user-facing messages such as price displays and status text. Under the language/locale policy, this can be a natural-language policy issue because the skill appears to assume a single language without documenting user choice or opt-in.

Content

No source excerpt is available for this finding.