ring-device-settings-librarynpm
ring-device-settings-library is a confirmed malicious npm package (MAL-2026-15520) that executes malicious code on install (malicious versions 30.0.0, 45.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in ring-device-settings-library (npm)
What this malware does
package.json declares a dependency whose key equals the package's own name (ring-device-settings-library) and whose value is a raw HTTPS URL pointing at an off-registry host: https://repo.securityctrl.com/ring-device-settings-library. On npm install, npm resolves that URL rather than a registry version range and installs whatever bytes the host returns, running any lifecycle scripts contained in the fetched artifact. There is no version pin, no integrity hash, and no signature check, and the host is unrelated to any npm registry. The shipped package contents are otherwise an inert placeholder, so the manifest line is the entire installed surface: whoever controls repo.securityctrl.com controls the code that executes on the installer's machine on every install. The self-referential dependency name, combined with the implausibly high version (45.0.0), is also a dependency-confusion shape that can win resolution against an internally-named package.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ring-device-settings-library (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ring-device-settings-library across your stack and pipelines.
If you installed it — respond
Remove ring-device-settings-library from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If ring-device-settings-library was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks ring-device-settings-library before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks ring-device-settings-library-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.