diff --git a/docs/connect-blockchain/near/web.mdx b/docs/connect-blockchain/near/web.mdx
index ab7e9fd1e..18a0f46d9 100644
--- a/docs/connect-blockchain/near/web.mdx
+++ b/docs/connect-blockchain/near/web.mdx
@@ -92,7 +92,7 @@ provider for Near in Web3Auth, so we must use the private key to make RPC calls
 To access the user's private key, the application can use the function
 `web3auth.provider.request({method: "private_key"})` from the Web3Auth provider. Yet, this key
 cannot be used with Near since it requires the `ed25519` key. Therefore, we must use the
-`getED25519Key()` function from `@toruslabs/openlogin-ed25519` to convert the `secp256k1` key to an
+`getED25519Key()` function from `@web3auth/base-provider` to convert the `secp256k1` key to an
 `ed25519` key.
 
 ```tsx
diff --git a/docs/features/server-side-verification.mdx b/docs/features/server-side-verification.mdx
index a3511d5b6..3f6d00280 100644
--- a/docs/features/server-side-verification.mdx
+++ b/docs/features/server-side-verification.mdx
@@ -239,7 +239,7 @@ const app_pub_key = getPublicCompressed(
 <TabItem value="ed25519">
 
 ```ts
-import { getED25519Key } from "@toruslabs/openlogin-ed25519";
+import { getED25519Key } from "@web3auth/base-provider";
 
 const app_scoped_privkey = await web3auth.provider?.request({
   // focus-next-line
diff --git a/docs/migration-guides/tkey-v11-to-v15.mdx b/docs/migration-guides/tkey-v11-to-v15.mdx
index 519c3ded1..9965a1de0 100644
--- a/docs/migration-guides/tkey-v11-to-v15.mdx
+++ b/docs/migration-guides/tkey-v11-to-v15.mdx
@@ -99,11 +99,11 @@ from v15, developers can use the tKey with the Blockchain ecosystem which uses t
 :::warning
 
 Please note, this is a native support for `ed25519` curve in tKey SDK, unlike the previous
-integrations where, using the `openlogin-ed25519` package, a sub key was derived for supporting the
-curve.
+integrations where, using the `@web3auth/base-provider` package, a sub key was derived for
+supporting the curve.
 
-If you are already using the `openlogin-ed25519` package for your application, please do not upgrade
-to this method as **it might cause the keys to change** for existing users.
+If you are already using the `@web3auth/base-provider` package for your application, please do not
+upgrade to this method as **it might cause the keys to change** for existing users.
 
 For new integrations, we recommend using this new flow of native support for `ed25519` curve.
 
diff --git a/docs/sdk/pnp/react-native/usage.mdx b/docs/sdk/pnp/react-native/usage.mdx
index fc9482146..01dbc05b1 100644
--- a/docs/sdk/pnp/react-native/usage.mdx
+++ b/docs/sdk/pnp/react-native/usage.mdx
@@ -140,7 +140,7 @@ export type LoginParams = BaseRedirectParams & {
    *
    * Note: This parameter won't change format of private key returned by auth service. Private key returned
    * by auth service is always `secp256k1`. As of now you have to convert it to `'ed25519'` if you want.
-   * You can use `@toruslabs/openlogin-ed25519` npm package for this purpose.
+   * You can use `@web3auth/base-provider` npm package for this purpose.
    *
    *
    * @defaultValue secp256k1
diff --git a/src/common/sdk/pnp/web/_auth-login-settings.mdx b/src/common/sdk/pnp/web/_auth-login-settings.mdx
index 0ee3632e4..2d093ee44 100644
--- a/src/common/sdk/pnp/web/_auth-login-settings.mdx
+++ b/src/common/sdk/pnp/web/_auth-login-settings.mdx
@@ -70,7 +70,7 @@ export type LoginParams = BaseRedirectParams & {
    *
    * Note: This parameter won't change format of private key returned by auth. Private key returned
    * by auth is always `secp256k1`. As of now you have to convert it to `'ed25519'` if you want.
-   * You can use `@toruslabs/openlogin-ed25519` npm package for this purpose.
+   * You can use `@web3auth/base-provider` npm package for this purpose.
    *
    *
    * @defaultValue secp256k1