Live › package › GHSA-p7gq-mvm4-4cw4
Go to dashboardNot triaged yet. The sources’ own description is below.
First seen by InfraStack 2026-10-26 20:51 UTC. All times on this page are UTC.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| @ziedzzz/demo-canary | npm | = 1.0.0; = 0.0.0-stage | – |
Unknown from the sources.
Unknown from the sources.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
-= Per source details. Do not edit below this line.=-
On npm install, the package's declared postinstall script executes index.js, which collects a host fingerprint (hostname, username, home directory, cwd, platform/arch/OS release, CPU model, memory, network interfaces including MAC/OUI, process info) and enumerates process.env for variable names matching TOKEN|SECRET|KEY|PASS|AWS_|GCP_|AZURE_|SSH|GIT|NPM|DOCKER. The collected data is transmitted via HTTPS GET to the hardcoded third-party endpoint telegrambot-aebk.onrender.com/ping. The behavior fires automatically on install without opt-in and discloses the installer's host identity and credential-variable inventory to an author-controlled destination.
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
This page as .md · .json · in your agent: get_signal("GHSA-p7gq-mvm4-4cw4")