Which versions of @staticj/cropperxmjs are malicious?

The following npm versions of @staticj/cropperxmjs are flagged malicious: 1.6.0. Treat any of these as compromised.

How do I remediate @staticj/cropperxmjs if I installed it?

@staticj/cropperxmjs 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 @staticj/cropperxmjs — how do I know if it already compromised me?

If @staticj/cropperxmjs 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 @staticj/cropperxmjs part of a known attack campaign?

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

Malicious package

@staticj/cropperxmjsnpm

@staticj/cropperxmjs is a confirmed malicious npm package (MAL-2026-16081) that steals credentials and exfiltrates sensitive data (malicious version 1.6.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @staticj/cropperxmjs (npm)

MAL-2026-16081

Immediate action

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

npm uninstall @staticj/cropperxmjs

What this malware does

@staticj/[email protected] ships a modified cropper.min.js that impersonates the legitimate Cropper.js library. At library load, injected code reconstructs the URL https://u.myquickcash.shop/api/spt/upgrade from many single-letter string fragments interleaved with legitimate Cropper.js constants (Qt='https:', Kt='//u.', Vt='my', Ft='quick', Jt='cash', t='.shop', qt='/api/spt/', $t='upgrade') to defeat simple grep-based detection. It reads GM_info.script metadata (author, name, version, namespace, updateURL), URL-encodes it, and sends it via GM_xmlhttpRequest to that endpoint; the response body is passed to eval(), executing attacker-controlled JavaScript under Tampermonkey/Greasemonkey privileges (GM* APIs bypass CORS/CSP). Calls are rate-limited to 15/day using GM_setValue key 'sp_req_daily'. The exfiltrated updateURL identifies each victim userscript's auto-update channel, enabling targeted follow-on supply-chain attacks. Any userscript bundling this file exposes its end users to remote code execution controlled by the operator of u.myquickcash.shop.

Malicious versions

1 flagged

1.6.0

Indicators of compromise (SHA-256)

ac36a108b1e9c92a64955277bdfe9a09cdae61504e9a1bfaf40a15c50595139a

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

Campaign

IN-MAL-2026-019858

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @staticj/cropperxmjs-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

Explore

All malware advisories How O3 detects malware Vulnerability database