Inconsistent behavior across platforms when importing `node:http` after defining `Object.prototype['0']`

Version

24.10.0

Platform

Microsoft Windows NT 10.0.26200.0 x64

and

Linux KContainer 5.10.0-12-amd64 #1 SMP Debian 5.10.103-1 (2022-03-07) x86_64 x86_64 x86_64 GNU/Linux

Subsystem

No response

What steps will reproduce the bug?

Hi,

The behavior can be reproduced by running the following snippet:

Object.defineProperty(Object.prototype, '0', {   
     set() {
        console.log(123);        
     }
 });

import http from "node:http"

Run this code by creating a file a.js in Both Linux and Windows and observe a difference in output.

How often does it reproduce? Is there a required condition?

File extension must be .js
Use import http from "node:http" instead of const http = require('http');

What is the expected behavior? Why is that the expected behavior?

Code should give same output when run in both Linux and Windows

What do you see instead?

Linux:

root@KContainer:~/git/run/test# node test.js
123
(node:1547) [MODULE_TYPELESS_PACKAGE_JSON] Warning: Module type of file:///home/c01kele/git/run/test/test.js is not specified and it doesn't parse as CommonJS.
Reparsing as ES module because module syntax was detected. This incurs a performance overhead.
To eliminate this warning, add "type": "module" to /home/c01kele/package.json.
(Use `node --trace-warnings ...` to show where the warning was created)
123
123
123

Windows:

PS D:\HIWI\RESULTS\31_10_2025> node .\test.js
PS D:\HIWI\RESULTS\31_10_2025> 

If you use const http = require('http'); instead of import http from "node:http", both Linux and Windows give no output.

Additional information

No response

Start by running the issue's a.js reproduction with the node:http import on the reported Linux and Windows environments, then compare it with the require('http') case. Trace the built-in module import path involved in the platform difference; done means the same output is produced on both platforms without changing the reproduction.