Security audit
Security checks for vulnerabilities and agentic risk
This is a documentation-only LwM2M reference skill; the scanner alerts point to badges, protocol examples, and broad routing language rather than hidden or executable behavior.
Install this if you want LwM2M protocol expertise. Be aware it may activate for some general IoT device-management questions, and independently verify current OMA/GSMA/3GPP details before using guidance for production firmware updates, remote wipe/reboot, credential provisioning, or fleet operations.
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
<div align="center">
<!-- ============================================================ -->
<!-- GITHUB BANNER BADGES -->
<!-- ============================================================ -->
Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).
│ │
│ ... when shutting down ... │
│ │
│── DELETE /rd/a1b2c3 ───────────────────►│
│ (De-register) │
│ │
│◄── 2.02 Deleted ───────────────────────│
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
<div align="center">
[](https://star-history.com/#svdwalt007/Best-LwM2M-Agentic-Skills&Date)
</div>
The skill’s activation criteria explicitly extend beyond LwM2M-specific terms to generic phrases like device management, IoT protocol, constrained devices, and CoAP/OMA-adjacent context. That can cause the skill to activate in unrelated conversations and inject highly specialized protocol guidance where it was not intended, increasing the chance of scope hijacking, irrelevant authority bias, or bypass of a more appropriate domain-specific skill.
This markdown file documents operations such as decommission wipe/lock, firmware updates, software installs, and remote execute/reboot flows, all of which can affect device availability, integrity, or data. The document reads as a technical reference and does not include a clear warning section informing users that these actions are safety-critical and should be performed cautiously in controlled environments.
This is a manifest file, so vague-trigger checks apply. The description markets the skill as a comprehensive expert resource but gives no specific trigger phrases, invocation conditions, or exclusion scope, which could make routing to this skill overly broad for many general IoT or security-related requests.
No suspicious patterns detected.