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

form-bnpl-dolyame-component-objectnpm

Advisory published Updated

form-bnpl-dolyame-component-object is a confirmed malicious npm package (MAL-2026-12384) that executes malicious code on install (malicious version 20.8.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in form-bnpl-dolyame-component-object (npm)

MAL-2026-12384
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall form-bnpl-dolyame-component-object

What this malware does

On require() of the package, polyfill.js selects a platform-specific binary and downloads it over HTTPS from Cloudflare Workers subdomains whose hostnames are assembled via array-join string splits to defeat static detection (e.g. oob-worker.cf102-baf.workers.dev, cf101-adf.workers.dev, cf103-070.workers.dev, cf99-9b3.workers.dev), with a DNS-TXT fallback under *.dl.well1.site. The downloaded bytes are written to /tmp or %TEMP% under a disguised name (dotnet_diag<hex>.exe on Windows,.cache_<hex> on Unix), chmod 0755, and spawned detached via cp.spawn("/bin/sh", ["-c", fp + " &"], {detached:true}) or cmd.exe start /b. Environment-variable names such as DISABLE_TELEMETRY, ANALYTICS_OPT_OUT, and DO_NOT_TRACK are used as a cover story alongside an analytics_state TTL stamp. A second 81KB lib/telemetry.js bundle ships alongside containing the same cp.spawn + chmod 755 dropper pattern. The package's declared purpose is a BNPL form component, which does not require downloading and executing platform-specific binaries from anonymous workers.dev hosts.

Malicious versions

1 flagged
20.8.9

Indicators of compromise (SHA-256)

06f48cc3ab15e35aac9a2c38a8f16c695d84e17e2b742e99f5b0c0a3947a6cda

Detection & response playbook

Malicious package

  1. Find it

    Search your lockfiles and build artifacts for form-bnpl-dolyame-component-object (version 20.8.9).

  2. If you installed it — respond

    Remove form-bnpl-dolyame-component-object from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

  3. Did it already run?

    If form-bnpl-dolyame-component-object 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. form-bnpl-dolyame-component-object on npm has been identified as a malicious package (version 20.8.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014747

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks form-bnpl-dolyame-component-object-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database
form-bnpl-dolyame-component-object (npm) malicious package — MAL-2026-12384 | O3 Security