supply chain event / NVI-00015757 / Revision 1
Malicious code in layer2-sdk (npm)
GitHub lists this malware advisory for layer2-sdk, layer2-sdk. 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.
layer2-sdk
source listed= 1.0.0
## Source: amazon-inspector (1bd6521302fb3f49a8c444435a33834be40a420972df3a03cadb5fdb3176a68f) index.js line 75 decodes a base64-encoded string via Buffer.from(..., 'base64').toString('utf8') and passes the result to an evaluator, executing hidden code when the module is loaded. The obfuscated-and-exec'd blob pattern in a package presenting itself as a generic SDK is consistent with a supply-chain dropper: the actual behavior is concealed from casual inspection of the source and runs as a side effect of require()'ing the package. The package name suggests a blockchain/Layer-2 SDK, but the shipped code's only notable operation is decoding and executing an opaque payload. --- Credit: OpenSSF (source)
layer2-sdk
source listed= 1.0.1
## Source: amazon-inspector (1bd6521302fb3f49a8c444435a33834be40a420972df3a03cadb5fdb3176a68f) index.js line 75 decodes a base64-encoded string via Buffer.from(..., 'base64').toString('utf8') and passes the result to an evaluator, executing hidden code when the module is loaded. The obfuscated-and-exec'd blob pattern in a package presenting itself as a generic SDK is consistent with a supply-chain dropper: the actual behavior is concealed from casual inspection of the source and runs as a side effect of require()'ing the package. The package name suggests a blockchain/Layer-2 SDK, but the shipped code's only notable operation is decoding and executing an opaque payload. --- Credit: OpenSSF (source)
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-wvvm-5h3m-prf6 ↗
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.