Online Security

Marketplace account access

MALHUT configures marketplace account access during client onboarding under the signed service scope. Depending on the marketplace and assigned tasks, work is performed through supported delegated roles, limited-scope API credentials or controlled data exports. Public interface examples contain illustrative, non-client data and remain separate from each client's working environment.

Protect marketplace access

• ✓Do not send a marketplace primary password, recovery code or one-time authentication code to MALHUT.
• ✓Use the marketplace's supported delegated role or a limited-scope API credential where the marketplace provides one.
• ✓Grant only the permissions required for the agreed operating scope and set an expiry date where available.
• ✓Do not provide a Wildberries personal user token; use only the integration access method supported for the intended task.
• ✓Enable multi-factor authentication on the marketplace account and the email account used for recovery.
• ✓Revoke access promptly when the project or an authorised employee's involvement ends.

Verify MALHUT communications

Check that website links use the malhut.com domain. Treat unexpected requests for credentials, payments, file downloads or urgent access changes as suspicious. Confirm unusual instructions through a previously verified contact channel before acting.

Report a concern

If you suspect impersonation, credential exposure or unauthorised account activity, revoke the affected marketplace access first where possible, contact the marketplace's official support and notify MALHUT at Rafael@malhut.com. Do not include passwords, secret tokens or one-time codes in the message.

Security limits

MALHUT applies safeguards proportionate to the functions that are active, but no website, email channel or internet service can guarantee absolute security. Detailed controls, incident duties and access boundaries for a client project must be documented in the applicable signed agreement.