Unexpected MDM-like behavior and developer mode on retail MacBook M4

Hi all,


I have a MacBook M4 Pro recently purchased through Apple retail channels with AppleCare+ that is behaving as though it's an MDM provisioned device.


For example, wifi settings etc. changing without my involvement and what appear to be mdm related network calls. System Preferences show that no profiles or extensions are installed. The only software I've ever installed is Homebrew, Little Snitch, and Parallels.


The device is in Lockdown Mode with the MacOS firewall set to block all incoming network connections. I have logged the device into iCloud once to download (but not install) XCode with an AppleID that is not (to my knowledge) registered as an Apple Developer account.


Here are some of outputs from terminal:

  • spctl kext-consent status
    • Kernel Extension User Consent: ENABLED
  • spctl --status
    • assessments enabled
  • csrutil status
    • System Integrity Protection status: enabled.
  • devtoolssecurity -status
    • Developer mode is currently disabled.
  • log show --predicate 'eventMessage CONTAINS "AMFI"' --info --last 7d

AMFI: developer mode is force enabled on this platform


At this stage, I'm seeking help to understand the following:

  1. Is it expected for a retail purchased, non-provisioned device to be set up with developer mode force enabled?
  2. If this is an exploit, what type of exploit or exploit chain would lead to the mdm type behavior I experienced?
  3. What remediation steps (if any) are there?


Thanks in advance all.


I don't believe I'm able to @mention folks here, but gravityfed and MrHoffman appear to have been engaged in a related thread, Factory reset macmini M1 2020 is not like… - Apple Community, that went unresolved.









[Re-Titled by Moderator]

Original Title: MDM type exploit? Non-provisioned retail purchased MacBook M4 shows signs of MDM. Device developer mode force enabled. Related?


MacBook Pro (M4)

Posted on Jul 10, 2025 2:32 PM

Reply
10 replies

Jul 24, 2025 11:34 PM in response to compy1

Developer mode is a setting to allow "permission for locally installed apps to run on iOS, iPadOS, visionOS, and watchOS devices" [1]. Based on the documentation, AMFI developer mode refers to the ability to run applications and code signed by Apple Developer certificates (it still doesn't allow arbitrary unsigned code).


On iOS, iPadOS, visionOS, and watchOS devices, you can't normally run applications signed directly by a developer (Apple re-signs applications themselves for distribution through the App Store). However, on macOS, you can run applications signed directly by a developer [2].


I have confirmed that on two physical machines and one VM I have running macOS 15.5 [3] that "AMFI: developer mode is force enabled on this platform" is present in the logs. I would imagine if you go back to an Apple store and get a new Mac it would also display this message.


Further, extracting com.apple.driver.AppleMobileFileIntegrity from the kernelcache on my 15.5 system and performing limited static analysis [4], it appears as though this is a fixed code execution path as part of AMFI initialization routines (meaning there is nothing that can turn this off). There are other branches that are gated behind certain configuration, namely kernel bootargs such as amfi_bring_up_mode, amfi_get_out_of_my_way, etc.


The log message itself: "AMFI: developer mode is force enabled on this platform"; to me if this were true configuration the message would likely not include "force" or "on this platform", which points towards it being a fixed (forced) value (on macOS platform).


So to specifically answer your questions:


1. Yes, a standard retail purchased Mac running macOS is expected to have AMFI developer mode force enabled. This appears to be expected behavior on the macOS platform, despite it sounding unusual.

2. This is not an exploit and unrelated to issues you may be experiencing, if any [5].

3. No remediation steps, see 1 & 2.


Based on the totality of the information, I believe that AMFI developer mode being force enabled is intended specifically on the macOS platform (and not on iOS, iPadOS, visionOS, or watchOS).



[1] Enabling Developer Mode on a device | Apple Developer Documentation


[2] Subject to certain criteria, such as notarization, see: https://developer.apple.com/documentation/security/notarizing-macos-software-before-distribution.


[3] sw_vers output:


% sw_vers

ProductName: macOS

ProductVersion: 15.5

BuildVersion: 24F74


[4] Full disclosure I'm a software engineer but I don't work in reverse engineering so my analysis could be flawed.


[5] You never provided details of the specific network calls that were made that are MDM-related in nature. I have personally had some macOS settings fail to persist or get reset on my system, usually from OS updates e.g. 15.4 to 15.5 (based on my purely anecdotal observations this is most often settings related to the application firewall and analytics/privacy).


Jul 10, 2025 4:52 PM in response to compy1

If you are having issue with your brand new Mac , return it for one that works as expect out of the box.


you have a limited 14 days for an exchange or refund for any reason—see Returns & Refunds Order status

Returns & Refunds - Shopping Help - Apple


Only items that have been purchased directly from Apple, either online or at an Apple Retail Store




ref: Review and delete configuration profiles - Apple Support



Jul 10, 2025 8:00 PM in response to lkrupp

@leroydouglas thanks for the suggestion. I've found that Enabling / disabling developer mode directly has no impact on the AMFI developer force enabled setting.


@ikrupp I bought two, actually.


Machine 1


A MacBook Pro from Apple.com as a certified refurbished unit (the one mentioned above) for store pickup. After the strange mdm type behavior I took it the Genius bar and Apple performed the following actions:


  • Fresh MacOS install
  • DFU restore
  • Logic board replacement


Developer mode force enabled persisted on the machine after each of the steps above.



Machine 2


Because of my experience with the MacBook Pro I went and purchased a MacBook Air M4 at the Cupertino visitor center store with AppleCare+ a few weeks ago. I performed the following evaluation:


  • Booted only into Recovery Mode <-- Note, I have yet to set the machine up with a local account.
  • While in recovery mode, I connected to the internet.
  • In terminal, I checked the AMFI logs and again saw developer mode force enabled. <-- see below


Jul 10, 2025 5:46 PM in response to compy1

compy1 wrote:

Unfortunately, the issues with the device didn't become apparent until outside the return window.

Thanks for sharing the link. There's never been any visible configuration profiles installed on the device.

Are you familiar with whether developer mode force enabled is expected for a retail, non-provisioned MacBook?


Disable Developer Mode:


"To disable Developer Mode on the device, go to Settings > Privacy & Security > Developer Mode and tap Developer Mode. Toggle the Developer Mode switch to the off position. After you disable Developer Mode, you can’t run apps from Xcode on the device until you enable Developer Mode again."



ref: Enabling Developer Mode on a device | Apple Developer Documentation



Your 90 days of complimentary telephone support begins on the date of purchase.

Call Customer Support  (800) MYAPPLE (800–692–7753)



always available —


 Customer Support  (800) MYAPPLE (800–692–7753)


or on line  https://getsupport.apple.com/


or call  AppleCare Support at 1-800-APLCARE (800-275-2273)


Outside the USA—Contact Apple for support and service by phone

See a list of Apple phone numbers around the world.

Contact Apple Support - Apple Support 



Jul 10, 2025 5:57 PM in response to compy1

"I have a MacBook M4 Pro recently purchased through Apple retail channels with AppleCare+ that is behaving as though it's an MDM provisioned device."


What retail channel exactly? Please explain in detail as to from where and from whom you purchased the MacBook because it looks to me like you bought a returned or formerly corporately owned MacBook.



Jul 11, 2025 8:56 AM in response to compy1

compy1 wrote:

Machine 2

Because of my experience with the MacBook Pro I went and purchased a MacBook Air M4 at the Cupertino visitor center store with AppleCare+ a few weeks ago. I performed the following evaluation:

Booted only into Recovery Mode <-- Note, I have yet to set the machine up with a local account.
• While in recovery mode, I connected to the internet.
• In terminal, I checked the AMFI logs and again saw developer mode force enabled. <-- see below


so are you saying as it turns — this not be an issue...

Jul 11, 2025 10:44 AM in response to leroydouglas

@leroydouglas I'm not sure I follow.


My ask of the community is help answering the following questions:


  1. Is it expected for a retail purchased, non-provisioned device to be set up with developer mode force enabled?
  2. If this is an exploit, what type of exploit or exploit chain would lead to the mdm type behavior I experienced?
  3. What remediation steps (if any) are there?



Jul 11, 2025 12:32 PM in response to leroydouglas

@leroydouglas Yes, I understand that it appears to be the default with my two Macs.


I don't believe that's the same thing as asserting that developer mode force enabled is the default on macOS for retail (non-business account, developer account, etc.) users.


Enabling Developer Mode on a device | Apple Developer Documentation


re: exploits. I make no claims as to diagnosing the situation. I'm asking questions and seeking help.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Unexpected MDM-like behavior and developer mode on retail MacBook M4

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.