other
- Location
scripts/track.py:29- Finding
Fabricated Package Events Presented as Tracking Results
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This package-tracking skill looks safe from a system-access perspective, but it advertises real-time tracking while returning locally invented delivery statuses.
Install only if you understand this behaves like a demo or mock tracker, not a real parcel-tracking service. Do not use its results for delivery decisions, customer notifications, refunds, or operational workflows unless the publisher replaces the simulation with real carrier lookups or clearly labels every result as simulated.
scripts/track.py:29Fabricated Package Events Presented as Tracking Results
scripts/track.py:53Terminal Control-Sequence Injection Through Unvalidated Tracking Numbers
The declared description presents the skill as a real parcel-tracking service with one-click logistics trajectory queries across many domestic and international couriers. However, the supplied code does not contact any carrier APIs or external services at all. Instead, it infers a carrier from regex/prefix patterns and returns fabricated demo events via simulate_tracking, explicitly labeled as 'Demo data - register for real carrier API for live tracking'. This is a material mismatch in primary functionality: simulated output versus real-time tracking. The code is otherwise aligned with the general domain of package tracking and does not show unrelated or suspicious undeclared capabilities, but the core promise of live tracking and broad carrier support is not actually implemented.
The skill advertises real-time package tracking across multiple carriers, but the implementation fabricates shipment events locally instead of querying any carrier or logistics API. This is dangerous because users may make decisions based on false delivery status information, and the mismatch between claimed functionality and actual behavior is deceptive.
The skill body presents its title, summary, features, and usage primarily in Chinese, with no statement that users may choose another language. Under the policy, forcing a specific language without user opt-in is a natural-language policy violation unless the locale restriction is clearly documented and justified.
The module docstring claims shipment tracking capability, but the code path only detects carrier-like formats and then generates synthetic timeline data. In the context of a package-tracking skill, this misleading representation increases the risk of user deception and undermines trust, even if it does not directly enable code execution or data theft.
No suspicious patterns detected.