Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Malicious code in velabuild (npm)

Exploitation and risk

Source status

CISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.

Which CVEs have scores here?

This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.

No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.

osv · MAL-2026-13493

Published

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (fa899acd5a63682964770cb32c4f0707008c9f3894ca6f5cacd222de74f03cea) cli.js embeds a base64-encoded RSA private key in CONFIG.encodedSSHKey, decodes it to a temp file with mode 0o600, and uses it to `ssh -o StrictHostKeyChecking=no -i <key> [email protected]` to invoke bash scripts under /home/ubuntu/signing-server for the CLI's signup/login/deploy subcommands. The private key is shipped identically to every installer of the package, so anyone who downloads the tarball obtains valid SSH credentials to the author's server. Installing or requiring the package does not read installer-side secrets, does not fetch or execute attacker-controlled code on the installer, and does not modify the installer's filesystem outside the package's own temp key file. A secondary observation: the `rx signup` / `rx login` subcommands pass user-supplied username and password as shell arguments to auth.sh over the shared SSH tunnel, but this only fires when the user explicitly invokes those subcommands and matches the package's documented auth backend. ## Source: ghsa-malware (3c64dbb041d6e5afb6472e08a1c6a3d31b123bdbb00d99bc8452e826848d4666) 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.

Source published
7 Aug 2026 00:06:23 UTC
Source modified
7 Aug 2026 12:35:24 UTC
Saved here
24 Oct 2026 13:17:17 UTC
Source terms
OSV · upstream source license applies

Original source record · Cite this exact observation · Complete original publisher JSON

Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 22 Nov 16:32 UTC · 274 of 275 readable · 270 fully read · documentation 469/469 current