Which versions of bimi-maker are malicious?

The following npm versions of bimi-maker are flagged malicious: 8.2.4. Treat any of these as compromised.

How do I remediate bimi-maker if I installed it?

bimi-maker establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed bimi-maker — how do I know if it already compromised me?

If bimi-maker 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 bimi-maker part of a known attack campaign?

Yes — bimi-maker is associated with the IN-MAL-2026-010504 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 bimi-maker 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 bimi-maker (version 8.2.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bimi-maker across your stack and pipelines.

Malicious package

bimi-makernpm

bimi-maker is a confirmed malicious npm package (MAL-2026-10579) that opens a backdoor for remote access (malicious version 8.2.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bimi-maker (npm)

MAL-2026-10579

Immediate action

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

npm uninstall bimi-maker

What this malware does

On npm install, the package's preinstall hook runs node index.js, which executes whoami and id via child_process and collects os.hostname(), os.userInfo(), os.platform(), homedir, cwd, and related host identifiers. The collected JSON payload is POSTed over HTTPS to a hardcoded Burp Collaborator subdomain, https://mqgby2y4jlp0k06gbpg1ulgjqaw1ks8h.oastify.com/detox56. The package ships no legitimate functionality matching its BIMI-related name; the only observable behavior is an install-time reconnaissance beacon to an attacker-controlled OAST endpoint, consistent with dependency-confusion or typosquat probing.

Malicious versions

1 flagged

8.2.4

Indicators of compromise (SHA-256)

4a4e6202887cfa87e6dcff6e37af854445a0e44f38b25ef6d3e40fec06cc8b5f

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bimi-maker (version 8.2.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bimi-maker across your stack and pipelines.
If you installed it — respond
bimi-maker establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If bimi-maker 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 bimi-maker 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. bimi-maker on npm has been identified as a malicious package (version 8.2.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010504

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks bimi-maker-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database