Which versions of int_sezzle_sfra are malicious?

The following npm versions of int_sezzle_sfra are flagged malicious: 25.2.1. Treat any of these as compromised.

How do I remediate int_sezzle_sfra if I installed it?

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

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

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

Malicious package

int_sezzle_sfranpm

Malicious code in int_sezzle_sfra (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-6577

Immediate action

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

npm uninstall int_sezzle_sfra

What this malware does

package.json declares preinstall: node index.js, which fires automatically on npm install. index.js collects host reconnaissance from the installer machine — hostname, OS info, username, uid/gid, shell, home directory, current working directory, and the output of whoami and id shelled out via child_process.exec — and POSTs the resulting JSON to a hardcoded Burp Collaborator OAST subdomain at https://1mopc72u2pqhsphbd3rmzirm9df43wrl.oastify.com/detox56. The package name mirrors the Salesforce Commerce Cloud (SFRA) cartridge naming convention used by Sezzle's internal int_sezzle_sfra integration cartridge; combined with empty author/description/license metadata and the install-time OAST beacon, this matches the canonical dependency-confusion pattern targeting a private vendor cartridge name. Installing this package causes unconsented exfiltration of installer identity and shell-command output to an attacker-controlled callback host.

Malicious versions

1 flagged

25.2.1

Indicators of compromise (SHA-256)

16242285e7dabb5a109f61e97ab52c05ad80ea9b8f326a706c3228268536e80d

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

Campaign

IN-MAL-2026-007749

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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