Which versions of sort-imports-es6-autofix are malicious?

Every published version of sort-imports-es6-autofix on npm is considered malicious. Remove the package entirely.

How do I remediate sort-imports-es6-autofix if I installed it?

Remove sort-imports-es6-autofix from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed sort-imports-es6-autofix — how do I know if it already compromised me?

If sort-imports-es6-autofix was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is sort-imports-es6-autofix part of a known attack campaign?

Yes — sort-imports-es6-autofix is associated with the GHSA-9w4p-mhx9-rcmp campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find sort-imports-es6-autofix across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for sort-imports-es6-autofix (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging sort-imports-es6-autofix across your stack and pipelines.

Malicious package

sort-imports-es6-autofixnpm

Malicious code in sort-imports-es6-autofix (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-104

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall sort-imports-es6-autofix

What this malware does

The package sort-imports-es6-autofix was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

93323a932d48f64cf4805c19517de157f47894cbba4fb9d7bce37adc8d3f1337

20061f2672fcbe82b13ab8e09c629d93991ef45200bb30c7bf9a1dc78cbb4230

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for sort-imports-es6-autofix (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging sort-imports-es6-autofix across your stack and pipelines.
If you installed it — respond
Remove sort-imports-es6-autofix from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If sort-imports-es6-autofix was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks sort-imports-es6-autofix before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. sort-imports-es6-autofix on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-9w4p-mhx9-rcmp

References

github.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks sort-imports-es6-autofix-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring