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

dotenv-packnpm

Malicious code in dotenv-pack (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-2900
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall dotenv-pack

What this malware does

dotenv-pack is a malicious npm package that when imported downloads a C2 dropper from https://api.npoint[.]io/5b357f718ab4ee355003 and executes it (similar to malware in to chai-await-test).

The package dotenv-pack was found to contain malicious code.

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

b57650f0341c4520703e30ebd6c256f564519680e225e8dabefcd48b4218dfa1

Detection & response playbook

Backdoor / remote access
  1. Find it

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

  2. If you installed it — respond

    dotenv-pack establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

  3. Did it already run?

    If dotenv-pack 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 dotenv-pack 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. dotenv-pack on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

References

Credits

  • Amazon Inspector · finder
  • indece · finder

Detect & block this

O3 blocks dotenv-pack-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

dotenv-pack (npm) malicious package — MAL-2026-2900 | O3 Security