Fix/downgrade reanimated

[Nodonisko]

Description

Related Issue

Resolve #10132 #10361

Screenshots:

[socket-security]

Updated dependencies detected. Learn more about Socket for GitHub ↗︎

Packages	Version	New capabilities	Transitives	Size	Publisher
react-native-reanimated	3.6.1...3.3.0	environment	+0/-0	2.4 MB	tomekzaw

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Issue	Package	Version	Note	Source
Environment variable access	react-native-reanimated	3.3.0	Env Vars: Location: lib/module/reanimated2/hook/useAnimatedStyle.js +11 more instances...	@shopify/[email protected] via package.json @shopify/[email protected] via suite-common/icons/package.json suite-common/icons/package.json suite-native/accounts/package.json suite-native/alerts/package.json @shopify/[email protected] via suite-native/app/package.json suite-native/app/package.json @shopify/[email protected] via suite-native/atoms/package.json suite-native/atoms/package.json suite-native/device-manager/package.json @shopify/[email protected] via suite-native/graph/package.json suite-native/graph/package.json suite-native/link/package.json suite-native/message-system/package.json @shopify/[email protected] via suite-native/module-accounts-import/package.json suite-native/module-accounts-import/package.json suite-native/module-accounts-management/package.json suite-native/notifications/package.json @shopify/[email protected] via suite-native/react-native-graph/package.json suite-native/react-native-graph/package.json @shopify/[email protected] via suite-native/receive/package.json suite-native/receive/package.json suite-native/test-utils/package.json suite-native/toasts/package.json @shopify/[email protected] via suite-native/transactions/package.json suite-native/transactions/package.json

Next steps

What is environment variable access?

Package accesses environment variables, which may be a sign of credential stuffing or data theft.

Packages should be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of package-name@version specifiers. e.g. @SocketSecurity ignore [email protected] bar@* or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore [email protected]