NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

@c1-ease/commercenpm

Advisory published Updated

@c1-ease/commerce is a confirmed malicious npm package (MAL-2026-20324) that opens a backdoor for remote access (malicious versions 2.0.0, 2.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @c1-ease/commerce (npm)

MAL-2026-20324
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @c1-ease/commerce

What this malware does

The package is a near-empty compatibility shim whose only real behavior is a callback beacon. package.json declares a postinstall hook that runs node beacon.cjs, and the main entry index.js invokes beacon.fire() as a top-level side effect on require. beacon.cjs POSTs host identifiers — os.hostname(), the install path (__dirname), process.cwd(), and process.version — to the hardcoded endpoint https://vmi3699893.contaboserver.net:8787/_ah/dc with TLS verification explicitly disabled (rejectUnauthorized: false). The rest of the module surface is a Proxy returning no-op functions so a consuming build does not crash. The destination is not associated with the @c1-ease scope's publisher, the beacon fires without caller opt-in on both install and import, and an in-source comment frames a completed build-with-callback as evidence of reach — consistent with a dependency-confusion / namespace-squat probe against internal @c1-ease/* package names.

Malicious versions

2 flagged
2.0.02.0.1

Indicators of compromise (SHA-256)

53ad1a63c646c9a77ee9895cd48949e95259674fc9c990f65524ff0fed5cd69e
bfd04dd69116b1d123a66e4b145a0a2c8a75070d8d250f5de931184b1f0ab58f

Detection & response playbook

Backdoor / remote access
  1. Find it

    Search your lockfiles and build artifacts for @c1-ease/commerce (2 malicious versions).

  2. If you installed it — respond

    @c1-ease/commerce 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.

  3. Did it already run?

    If @c1-ease/commerce was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @c1-ease/commerce on npm has been identified as a malicious package (versions 2.0.0, 2.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-022982IN-MAL-2026-022983

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @c1-ease/commerce-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Explore

@c1-ease/commerce (npm) malicious package — MAL-2026-20324 | O3 Security