siriusbeyond
Affected
- Versions:
1.0.0
Fixed versions
None listed
Fix
No fixed version is listed.
Advisory
Also known as: None
Malicious package Its source marks this package as malicious: it is not a vulnerability in a legitimate one.
Malicious code in siriusbeyond (npm)
---
_-= Per source details. Do not edit below this line.=-_
Source: amazon-inspector (6ce19ca17a48cf79dd094940533d1bff88413d44c945948d0041da15a5b61779)
package.json wires callback.js to both the preinstall and postinstall lifecycle hooks, so npm install siriusbeyond executes it automatically. callback.js collects hostname, username, platform, cwd, home directory, uid/gid/pid, network interface details, CI/cloud environment indicators, and a list of process.env variable names matching approximately 35 credential-shaped regexes (token, secret, key, password, aws, azure, gcp, npm, git, ssh, jwt, database, stripe, slack, discord, webhook, etc.), together with existence checks for.env,.npmrc, credentials, and secrets.json in the working directory. The collected payload is POSTed to api.telegram.org using a hardcoded bot token and chat id (chat 1064260758). A secondary channel base64-encodes a JSON blob of host, user, and CI fields and issues a dns.resolve() against <base64>.dc-callback.example.com, providing a DNS-tunnel exfil path when outbound HTTPS is blocked. Even though variable values are not sent, the disclosed variable names and credential-file inventory identify which secrets the installer holds and enable targeted follow-on attack.
Not rated by the source.
1.0.0None listed
No fixed version is listed.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: OpenSSF Malicious Packages · Apache-2.0