Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

@aiwfm/communitywfm.scripts.apinpm

@aiwfm/communitywfm.scripts.api is a confirmed malicious npm package (MAL-2026-16146) that steals credentials and exfiltrates sensitive data (malicious version 28.1.28). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @aiwfm/communitywfm.scripts.api (npm)

MAL-2026-16146
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @aiwfm/communitywfm.scripts.api

What this malware does

The package's preinstall script (build.js) assembles a remote hostname from split string fragments that resolve to dawn-salad-18c7.mikhail-nab.workers.dev, base64-encodes the full process.env, and POSTs it to that endpoint on npm install. The exfiltration is gated by sandbox-evasion filters that suppress the request when common analysis-environment signals are present (Chinese mirror registries such as taobao/npmmirror/cnpmjs/tencent, mitmproxy CA via NODE_EXTRA_CA_CERTS, /analysis paths, /root HOME combined with /app PWD, or fewer than ten environment variables). On developer and CI machines process.env routinely contains npm auth tokens, cloud credentials, and other secrets, so this constitutes bulk credential and environment exfiltration to an attacker-controlled Cloudflare Workers endpoint.

Malicious versions

1 flagged
28.1.28

Indicators of compromise (SHA-256)

405cd17e3c682b1341db44361500ea68d80e1758f15387d9971d0af95f0c8a48

Detection & response playbook

Credential / info stealer

  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @aiwfm/communitywfm.scripts.api (version 28.1.28). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @aiwfm/communitywfm.scripts.api across your stack and pipelines.

  2. If you installed it — respond

    @aiwfm/communitywfm.scripts.api 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.

  3. Did it already run?

    If @aiwfm/communitywfm.scripts.api 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.

  4. How O3 protects you

    O3 blocks @aiwfm/communitywfm.scripts.api 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. @aiwfm/communitywfm.scripts.api on npm has been identified as a malicious package (version 28.1.28 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020021

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @aiwfm/communitywfm.scripts.api-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
@aiwfm/communitywfm.scripts.api (npm) malicious package — MAL-2026-16146 | O3 Security