supply chain event / NVI-00010513 / Revision 1
Malicious code in ksp-app (npm)
GitHub lists this malware advisory for ksp-app. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.
This report has not inspected your inventory, configuration, deployed build, reachability or evidence. A catalog listing and a severity score do not establish exposure or compromise.
01 / Meaning
Why it matters
Published affected context helps an owner decide what evidence to gather. This report has not examined your application.
02 / Applicability
The affected context
Affected versions, configuration prerequisites and known exclusions are public. Confirm each one against the deployed service.
ksp-app
source listed= 100.100.100
## Source: amazon-inspector (b14a9fbd9fc1a48dc3ac0498f9606cecb1a56bad912c7f8a818fad332ef9ad15) ksp-app@100.100.100 is a dependency-confusion-shaped npm package whose only payload is an opaque prebuilt Linux x64 native addon loaded at install time. package.json declares scripts.postinstall="node postinstall.js", which require()s prebuilds/linux-x64/addon.node. The tarball ships no C/C++ source, no binding.gyp, and no build tooling; index.js exports an empty object, so the entire package behavior is in the native binary. On load, the ELF addon reads the environment variables HOSTNAME, npm_package_name, and npm_config_registry and POSTs them over a raw socket to the hardcoded bare-IP endpoint http://64.181.165.115/dc (HTTP/1.0, Host: 64.181.165.115, format string h=%.40s&p=%.40s&u=%.20s&r=%.80s). The version string 100.100.100, inert JS stub, generic "Frontend utilities" description, and a beacon that reports the installer's configured npm registry are the signature of a dependency-confusion exfiltration package used to confirm installs inside victim environments and disclose internal registry URLs to a third party. --- Credit: OpenSSF (
03 / Response
What to do next
- investigate
Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.
Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system. GitHub Advisory Database
A fixed release is not deployment evidence.
Check current vendor support and compatibility. After making a change, verify the deployed build and relevant runtime conditions. Keep the evidence, owner and time. An updated lockfile alone does not prove what is running.
04 / Limits
What this report cannot establish
- Customer inventory, deployment, reachability and exploitation have not been inspected.
05 / Provenance
Sources you can inspect
Each assertion retains its source. Mirrored records may repeat one underlying publisher; additional links are not independent corroboration.
- GHSA-2f2f-3rf8-8fgc ↗
GitHub Advisory Database · vendor advisory
Observed . GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.
Public revision history
Only published revisions appear here. Routine fetches do not create a material-change event.
- Revision 1 ·
First indexed by Null; source disclosure date is shown separately.