ls command in cowrie shell does not have working -h flag

[n0kovo]

I'm seeing a lot of attack scripts disconnecting from the system after executing:
which ls followed by ls -lh $(which ls)

In the Cowrie shell, the output of which ls is:
/bin/ls

and the output of ls -lh $(which ls) is:
-rwxr-xr-x 1 root root 112700 2013-04-05 11:52 ls

In a real bash shell, the output of ls -lh $(which ls) is:
-rwxr-xr-x 1 root root 144K Sep 24 2020 /usr/bin/ls

Is Cowrie not handling ls -lh $(which ls) correctly?
It would seem that the attacking script is comparing the output of the two commands, realising it's in a honeypot and aborting.

How do I get Cowrie to output -rwxr-xr-x 1 root root 144K Sep 24 2020 /usr/bin/ls when running ls -lh $(which ls)?

[micheloosterhof]

To do this the ls command needs to be updated in src/cowrie/commands/fs.py.

[micheloosterhof]

To make this fully work, the ls command needs to have a working -h flag, -h for human output will print the output in Kilobyte or Megabyte.

[AJ-Acevedo]

To do this the ls command needs to be updated in src/cowrie/commands/fs.py.

Does the ls command need to be updated in src/cowrie/commands/fs.py or did you mean src/cowrie/commands/ls.py?