registry / Credential exfiltration / siriusbeyond
siriusbeyond
SECURITY RESEARCH - Dependency Confusion PoC - Contact: ajmalaboobacker00@gmail.com
This report shows the evidence for siriusbeyond@1.0.0, the only known version.
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThis is concrete, unconsented install-time data exfiltration with redundant network channels. The package's research label does not neutralize the automatic behavior.
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 preinstall or postinstall execution.
Impact
Installing the package exposes identifying system, environment, and project-presence metadata to an external operator without user interaction.
Mechanism
callback.js builds host telemetry, posts it to Telegram, then performs a DNS lookup whose subdomain contains encoded host, user, and CI data.
Attack narrative
The package automatically runs a callback before and after installation. That callback inventories the installation host and environment, posts the resulting message to an operator-controlled Telegram bot, and attempts DNS-based metadata export as a fallback. Errors are suppressed, reducing visibility of the activity.
AI rationale
This is concrete, unconsented install-time data exfiltration with redundant network channels. The package's research label does not neutralize the automatic behavior.
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 runs callback.js automatically during both preinstall and postinstall.
- The callback builds a payload containing host, user, working-directory, home-directory, CI/cloud, environment-name, file-presence, network, and process metadata.
- The callback sends the payload to Telegram using an HTTPS POST request.
- The callback also encodes host, user, and CI information into a DNS lookup.
Evidence against
Behavioral surface
EnvironmentVarsFilesystemNetwork
HighEntropyStrings
Source & flagged code
10 flagged · loading sourcepackage.jsonView file
•scripts.preinstall = 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
Findings
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
Affected versions and remediation
This report applies to siriusbeyond@1.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing siriusbeyond@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.