Malicious code in csec-crypto-toolkit (npm)
What to do
Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
npm csec-crypto-toolkit
- Affected
- every version
- Fixed in
- no fixed version recorded
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record MAL-2026-18351 lists affected ranges: npm csec-crypto-toolkit >=0
VerifiedObserved Structured OSV record; not marked as GitHub-reviewed.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- not scored
- EPSS
- No dated EPSS signal available.
Source description
As published by the source; long descriptions are shortened.
--- _-= Per source details. Do not edit below this line.=-_
Source: amazon-inspector (2abb8bc55cfdb0121f6d5699665198f00bd78fbbaa555a695f2fe5188c733ef5) Package csec-crypto-toolkit version 0.0.0-stage ships two files and no detectable installer-harm behavior. No lifecycle scripts (preinstall/install/postinstall/prepare) that fetch or execute remote content were observed, no credential or environment-variable harvesting was observed, no network beacons to attacker-controlled destinations were observed, and no dropper, backdoor, or self-propagation mechanisms were observed. The version suffix `0.0.0-stage` is consistent with a placeholder/staging publish rather than a functional release.
Source: ghsa-malware (89ca44b227ea4da53f945de70efac936762435c8450545c64bc0272d97299e69) 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…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from osv record MAL-2026-18351
- Revision 1 · created ·
Published from osv record MAL-2026-18351
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: GHSA-v383-2358-576w Advisory: Malicious code in csec-crypto-toolkit (npm) IDs: GHSA-v383-2358-576w Record: https://patchnext.com/advisories/mal-2026-18351 (revision 2, source checked 30 Oct 2026, 06:05 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Unrated Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed. ## Affected components - npm csec-crypto-toolkit: affected every version ## Suggested inspection (read-only) - `npm ls csec-crypto-toolkit --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`. ## Supported action No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on csec-crypto-toolkit. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/MAL-2026-18351 (OSV record MAL-2026-18351 lists affected ranges: npm csec-crypto-toolkit >=0) Commands are suggestions: review each one before running it.
Loading voting…