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

csa-mfanpm

csa-mfa is a confirmed malicious npm package (MAL-2026-16175) that executes malicious code on install (malicious versions 1.1.15, 1.1.16). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in csa-mfa (npm)

MAL-2026-16175
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall csa-mfa

What this malware does

package.json declares a preinstall script that runs wget against http://169.58.142.14:8080/ with query parameters populated by shell command substitution of whoami, ls, and hostname. On npm install this automatically transmits the installer's username, current-directory listing, and hostname to a hardcoded bare-IP HTTP endpoint unrelated to any legitimate publisher infrastructure. There is no functional package purpose served by this behavior.

Malicious versions

2 flagged
1.1.151.1.16

Indicators of compromise (SHA-256)

127e5aef88d9d0461a01b970500dcf6a839b1e89a93c0b6578216cdc98058c09
959d2728ff38a804033ca7e07235b3a14bce65bd0e948077ba148a53c6cccff9

Detection & response playbook

Malicious package
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for csa-mfa (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging csa-mfa across your stack and pipelines.

  2. If you installed it — respond

    Remove csa-mfa 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 csa-mfa 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 csa-mfa 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. csa-mfa on npm has been identified as a malicious package (versions 1.1.15, 1.1.16 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020067IN-MAL-2026-020068

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks csa-mfa-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.

Explore

csa-mfa (npm) malicious package — MAL-2026-16175 | O3 Security