registry / Install hook abuse / byted-commerce-materials
byted-commerce-materials
SECURITY RESEARCH - Dependency Confusion PoC - Contact: ajmalaboobacker00@gmail.com
This report shows the evidence for byted-commerce-materials@1.0.0, the only known version.
AI Security Review
scanned 1mo ago · by lpm-firewall-aiAutomatic install-time host reconnaissance and covert transmission to hard-coded external endpoints are concrete malicious behavior. Error suppression and a DNS fallback reinforce the intent to collect installation telemetry without consent.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review; source fingerprint signature matched known malicious package; routed for review
Trigger
npm installation invokes the preinstall or postinstall lifecycle hook.
Impact
An installer’s host and deployment context is disclosed to an unrelated operator during package installation.
Mechanism
callback.js gathers system, CI, cloud, network, environment-name, and file-presence metadata, posts it to a hard-coded Telegram bot, and issues an encoded DNS lookup.
Attack narrative
Installing the package automatically launches callback.js before and after installation. It fingerprints the machine and deployment environment, checks for sensitive configuration filenames, then silently posts a formatted report to a Telegram bot. If HTTPS is blocked, it sends selected host, user, and CI data through a DNS query. The declared research purpose does not establish consent for this automatic external reporting.
AI rationale
Automatic install-time host reconnaissance and covert transmission to hard-coded external endpoints are concrete malicious behavior. Error suppression and a DNS fallback reinforce the intent to collect installation telemetry without consent.
Evidence
package.jsoncallback.js
Network endpoints2
api.telegram.orgdc-callback.example.com
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- The package automatically runs callback.js during both preinstall and postinstall, suppressing errors.
- The callback fingerprints the installing host, user, working and home directories, CI/cloud context, network addresses, sensitive environment-variable names, and presence of credential-related files.
- It sends the collected report to a hard-coded Telegram bot endpoint.
- It also encodes host, user, and CI data into a DNS query as a fallback exfiltration path.
Evidence against
- The code collects environment-variable names and file presence rather than reading their contents.
- The main entrypoint only exports metadata and logs messages.
Behavioral surface
EnvironmentVarsFilesystemNetwork
HighEntropyStrings
Source & flagged code
10 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node callback.js 2>/dev/null || true
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.preinstall = node callback.js 2>/dev/null || true
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkg•scripts.postinstall = node callback.js 2>/dev/null || true
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgcallback.jsView file
4*/
L5: const https = require('https');
L6: const os = require('os');
L7: const dns = require('dns');
L8: const fs = require('fs');
...
L12: const CHAT_ID = '1064260758';
L13: const PKG_NAME = process.env.npm[redacted] || 'unknown';
L14:
...
L17: const indicators = {
L18: 'GitHub Actions': process.env.GITHUB_ACTIONS,
L19: 'GitLab CI': process.env.GITLAB_CI,
...
L62: /auth/i, /api/i, /aws/i, /azure/i, /gcp/i, /google/i,
Critical
Hardcoded Runtime Data Exfiltration
Source sends credentials or rich application records to a package-controlled external receiver enabled by default.
callback.jsView on unpkg · L44*/
L5: const https = require('https');
L6: const os = require('os');
L7: const dns = require('dns');
L8: const fs = require('fs');
...
L12: const CHAT_ID = '1064260758';
L13: const PKG_NAME = process.env.npm[redacted] || 'unknown';
L14:
...
L17: const indicators = {
L18: 'GitHub Actions': process.env.GITHUB_ACTIONS,
L19: 'GitLab CI': process.env.GITLAB_CI,
...
L62: /auth/i, /api/i, /aws/i, /azure/i, /gcp/i, /google/i,
Critical
Credential Exfiltration
Source appears to send environment or credential material to an external endpoint.
callback.jsView on unpkg · L44*/
L5: const https = require('https');
L6: const os = require('os');
L7: const dns = require('dns');
L8: const fs = require('fs');
...
L12: const CHAT_ID = '1064260758';
L13: const PKG_NAME = process.env.npm[redacted] || 'unknown';
L14:
...
L17: const indicators = {
L18: 'GitHub Actions': process.env.GITHUB_ACTIONS,
L19: 'GitLab CI': process.env.GITLAB_CI,
...
L62: /auth/i, /api/i, /aws/i, /azure/i, /gcp/i, /google/i,
Critical
Dns Exfiltration
Source appears to send environment or credential material through DNS lookups.
callback.jsView on unpkg · L44Trigger-reachable chain: scripts.preinstall -> callback.js
L4: */
L5: const https = require('https');
L6: const os = require('os');
L7: const dns = require('dns');
L8: const fs = require('fs');
...
L12: const CHAT_ID = '1064260758';
L13: const PKG_NAME = process.env.npm[redacted] || 'unknown';
L14:
...
L17: const indicators = {
L18: 'GitHub Actions': process.env.GITHUB_ACTIONS,
L19: 'GitLab CI': process.env.GITLAB_CI,
...
L62: /auth/i, /api/i, /aws/i, /azure/i, /gcp/i, /google/i,
Critical
Trigger Reachable Dangerous Capability
A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
callback.jsView on unpkg · L44Trigger-reachable credential exfiltration chain: scripts.preinstall -> callback.js
L4: */
L5: const https = require('https');
L6: const os = require('os');
L7: const dns = require('dns');
L8: const fs = require('fs');
...
L12: const CHAT_ID = '1064260758';
L13: const PKG_NAME = process.env.npm[redacted] || 'unknown';
L14:
...
L17: const indicators = {
L18: 'GitHub Actions': process.env.GITHUB_ACTIONS,
L19: 'GitLab CI': process.env.GITLAB_CI,
...
L62: /auth/i, /api/i, /aws/i, /azure/i, /gcp/i, /google/i,
High
Trigger Reachable Credential Exfiltration
A manifest entrypoint or package-local install chain reaches credential exfiltration behavior.
callback.jsView on unpkg · L4•matchType = normalized_sha256
matchedPackage = commerce-materials@1.0.0
matchedPath = callback.js
matchedIdentity = npm:Y29tbWVyY2UtbWF0ZXJpYWxz:1.0.0
similarity = 1.000
summary = normalized source hash matched finalized malicious source
High
Known Malware Source Similarity
Source file is highly similar to a previously finalized malicious package; route for source-aware review.
callback.jsView on unpkg•matchType = malicious_source_fingerprint_signature
signature = 5069e151b9cf5006
signatureType = suspicious_hashes
sourceLabel = final_verdict:malicious
matchedPackage = commerce-materials@1.0.0
matchedPath = callback.js
matchedIdentity = npm:Y29tbWVyY2UtbWF0ZXJpYWxz:1.0.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.
callback.jsView on unpkgFindings
4 Critical4 High5 Medium3 Low
CriticalHardcoded Runtime Data Exfiltrationcallback.js
CriticalCredential Exfiltrationcallback.js
CriticalDns Exfiltrationcallback.js
CriticalTrigger Reachable Dangerous Capabilitycallback.js
HighInstall Time Lifecycle Scriptspackage.json
HighTrigger Reachable Credential Exfiltrationcallback.js
HighKnown Malware Source Similaritycallback.js
HighKnown Malware Source Fingerprint Signaturecallback.js
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
Affected versions and remediation
This report applies to byted-commerce-materials@1.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing byted-commerce-materials@1.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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.