Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

@avigilon/node-webrtcnpm

Advisory published Updated

@avigilon/node-webrtc is a confirmed malicious npm package (MAL-2026-15865) that opens a backdoor for remote access (malicious versions 2.1.4, 2.1.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @avigilon/node-webrtc (npm)

MAL-2026-15865
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @avigilon/node-webrtc

What this malware does

package.json declares a preinstall hook that runs index.js on npm install. index.js requires os, dns, https, querystring, and the package's own package.json, then collects host identifiers (os.hostname(), os.userInfo().username, os.homedir(), dns.getServers(), the package path and package.json contents) and POSTs them via https to the hardcoded host mj9ouelpgm0d26s3wp0syow03r9ix8lx.burp.attack.live. The package under the @avigilon scope exposes no other advertised functionality, and the destination is an unrelated third-party collector subdomain rather than any Avigilon or Motorola infrastructure. The shape matches a dependency-confusion reconnaissance beacon targeting an internal @avigilon/node-webrtc name.

Malicious versions

2 flagged
2.1.42.1.5

Indicators of compromise (SHA-256)

4aa3c859995de66617d9d96dcde2a176eb5f1cef9f96dbc9e85b09e85116b2fd
856277989637849346e759b8d07577326b164b5521ee643a84d704a457ad9f87

Detection & response playbook

Backdoor / remote access
  1. Find it

    Search your lockfiles and build artifacts for @avigilon/node-webrtc (2 malicious versions).

  2. If you installed it — respond

    @avigilon/node-webrtc establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

  3. Did it already run?

    If @avigilon/node-webrtc was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @avigilon/node-webrtc on npm has been identified as a malicious package (versions 2.1.4, 2.1.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-019401IN-MAL-2026-019400

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @avigilon/node-webrtc-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Explore

@avigilon/node-webrtc (npm) malicious package — MAL-2026-15865 | O3 Security