Which versions of @avigilon/node-webrtc are malicious?

The following npm versions of @avigilon/node-webrtc are flagged malicious: 2.1.4, 2.1.5. Treat any of these as compromised.

How do I remediate @avigilon/node-webrtc if I installed it?

@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.

I already installed @avigilon/node-webrtc — how do I know if it already compromised me?

If @avigilon/node-webrtc 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.

Is @avigilon/node-webrtc part of a known attack campaign?

Yes — @avigilon/node-webrtc is associated with the IN-MAL-2026-019401, IN-MAL-2026-019400 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @avigilon/node-webrtc across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @avigilon/node-webrtc (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @avigilon/node-webrtc across your stack and pipelines.

Malicious package

@avigilon/node-webrtcnpm

@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

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @avigilon/node-webrtc (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @avigilon/node-webrtc across your stack and pipelines.
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.
Did it already run?
If @avigilon/node-webrtc 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 @avigilon/node-webrtc 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

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database