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

[kevgeoleo]

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

[arturgawlik]

hey @kevgeoleo 👋 from my tests it seems that there is no difference between linux VS windows OS in this context. Also from my debugging session it seems that described differences between require VS import has nothing to do with that how those module systems are loading scripts, but generally what is important in Your provided example is that in import case there is message written to the terminal, and since writing to the terminal is a internally in node.js async operation it involves async_hooks which in this concrete example is setting in some internal array element with index 0 which is triggering Your defined property setter.
Because of the above I don't think that this is an a bug, and there is also no differences beetwen OS'es. But please correct me if I'm missing something here 😅

[ljharb]

It's arguably a bug, but objectively it's that node's core modules aren't consistently hardened against modification of builtins.

This behavior can be fixed, but it would require the use of primordials in the http code.

[gurgunday]

Yeah http code mostly lacks primordials