GHSA-jp74-4rg3-7ppj: Malicious code in react-native-drago-callkit (npm)
--- -= 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 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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Remove
Remove
npm/react-native-drago-callkitfrom your environment.Remove the react-native-drago-callkit package; removing it may not remove all malicious software resulting from its installation.
- Operational
Rotate all secrets and keys stored on the affected computer immediately, using a different computer.
Event History
Frequently Asked Questions
Does the available package analysis confirm malicious behavior in version 0.0.0-stage?
No. The analysis of version 0.0.0-stage found only two files and no observable installer-harm behavior, lifecycle scripts, secret collection, network calls, data relay, persistence mechanism, backdoor, or bundled credentials. It characterizes that version as consistent with a pre-release staging placeholder.
What should responders do if the package is installed or has run?
The GHSA malware source advises treating the computer as fully compromised. Rotate all secrets and keys from a different computer and remove the package; removal alone may not eliminate malicious access if the system was compromised.
Which package versions can be confirmed as affected from this information?
The provided data does not establish a definitive affected-version range. It specifically analyzes 0.0.0-stage and references npm pages for versions 1.0.15 and 1.0.16, but does not state which of those versions are malicious.