Which versions of imgbundle are malicious?

The following npm versions of imgbundle are flagged malicious: 1.0.0, 1.0.1. Treat any of these as compromised.

How do I remediate imgbundle if I installed it?

imgbundle carries a destructive/sabotage payload. Remove it immediately, restore any affected data from clean backups, and verify integrity of build outputs that may have been tampered with.

I already installed imgbundle — how do I know if it already compromised me?

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

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

Malicious package

imgbundlenpm

imgbundle is a confirmed malicious npm package (MAL-2026-17330) that runs destructive / sabotage code (malicious versions 1.0.0, 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in imgbundle (npm)

MAL-2026-17330

Immediate action

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

npm uninstall imgbundle

What this malware does

The package advertises itself as an image bundler, but index.js performs no image bundling. On require, a top-level IIFE reads an AES-256-CBC-encrypted file at cdn-img-fetch/.cache/banner.jpg inside the sibling dependency cdn-img-fetch, decrypts it with a hardcoded key derived from sha256('nif-runtime-2027'), writes the plaintext to cdn-img-fetch/.runtime/rt.jpg, deletes the source file, and registers an fs.watch on the source directory so the decrypt-and-stage step still fires if the encrypted blob is delivered later. The package also calls cif.ensureCached() on the cdn-img-fetch dependency in an error-recovery path, wiring the two packages together as a coordinated staged dropper: cdn-img-fetch supplies the encrypted bytes and imgbundle acts as the decoder that materializes attacker-controlled content onto the installer's filesystem at import time. The README description of image bundling does not correspond to any code path in the module, and hardcoded-AES-key decryption of an opaque blob from another package is not a legitimate implementation of that stated purpose.

Malicious versions

2 flagged

1.0.01.0.1

Indicators of compromise (SHA-256)

1577a61d49bcd6bd941dc6901b176730252973766b198f2065baea643ca81a16

e14218599b46d143fa8e150156864d14d58c327bd8a8816221ac4e8c5cc99350

Detection & response playbook

Destructive / sabotage

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for imgbundle (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging imgbundle across your stack and pipelines.
If you installed it — respond
imgbundle carries a destructive/sabotage payload. Remove it immediately, restore any affected data from clean backups, and verify integrity of build outputs that may have been tampered with.
Did it already run?
If imgbundle 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 imgbundle 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. imgbundle on npm has been identified as a malicious package (versions 1.0.0, 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020810IN-MAL-2026-020809

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks imgbundle-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

Explore

All malware advisories How O3 detects malware Vulnerability database