Malicious code in react-native-drago-callkit (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 react-native-drago-callkit
- Affected
- >= 1.0.16, <= 1.0.16>= 1.0.15, <= 1.0.15>= 1.0.2, <= 1.0.2>= 1.0.1, <= 1.0.1>= 1.0.0, <= 1.0.0>= 0.0.0-stage, <= 0.0.0-stage
- Fixed in
- no fixed version recorded
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record MAL-2026-18394 lists affected ranges: npm react-native-drago-callkit >=1.0.16 =1.0.15 =1.0.2 =1.0.1 =1.0.0 =0.0.0-stage <=0.0.0-stage
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 (b9df4250c447fe422966a254b974db832e444643ae8a106e29266ef04e55a51b) Package react-native-drago-callkit at version 0.0.0-stage ships only two files and exhibits no observable installer-harm behavior. There are no lifecycle scripts fetching or executing remote content, no reads of installer secrets (environment, ~/.aws, ~/.ssh, ~/.npmrc, browser or wallet stores), no network calls to hardcoded author or third-party endpoints, no silent relay of caller-supplied data, no persistence or backdoor mechanism, and no credentials shipped in the tarball. The version string and tiny file count are consistent with a pre-release staging placeholder.
Source: ghsa-malware (6482c5b9acc843621591425f84d7a79b5d1aef6d5c71f88c9d02074aa73afc6a) 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…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from osv record MAL-2026-18394
- Revision 1 · created ·
Published from osv record MAL-2026-18394
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-jp74-4rg3-7ppj Advisory: Malicious code in react-native-drago-callkit (npm) IDs: GHSA-jp74-4rg3-7ppj Record: https://patchnext.com/advisories/mal-2026-18394 (revision 2, source checked 31 Oct 2026, 06:00 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 react-native-drago-callkit: affected >= 1.0.16, <= 1.0.16; >= 1.0.15, <= 1.0.15; >= 1.0.2, <= 1.0.2; >= 1.0.1, <= 1.0.1; >= 1.0.0, <= 1.0.0; >= 0.0.0-stage, <= 0.0.0-stage ## Suggested inspection (read-only) - `npm ls react-native-drago-callkit --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 react-native-drago-callkit. - 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-18394 (OSV record MAL-2026-18394 lists affected ranges: npm react-native-drago-callkit >=1.0.16 =1.0.15 =1.0.2 =1.0.1 =1.0.0 =0.0.0-stage <=0.0.0-stage) Commands are suggestions: review each one before running it.
Loading voting…