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

ppt-creatornpm

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

MAL-2026-6355
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall ppt-creator

What this malware does

On npm install, package.json's preinstall hook runs index.js, which collects host identifiers (os.hostname(), os.userInfo(), homedir, DNS servers, __dirname, the package's own package.json) and reads the contents of /etc/passwd and /etc/hosts, then HTTPS-POSTs the resulting JSON to a Burp Collaborator subdomain at 3z3l99x7vp8us6lzqm575hfh58bzzqnf.oastify.com. The package has no documented purpose and no library functionality — its only effect on installers is the exfiltration beacon. Any developer or CI system that runs npm install ppt-creator leaks user-account enumeration data and host fingerprints to the attacker-controlled collaborator endpoint.

Malicious versions

1 flagged
1.0.0

Indicators of compromise (SHA-256)

8040bc58597dee52581beb232688c85302554af0af5726abc15c56a21ac69f2c

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 ppt-creator (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ppt-creator across your stack and pipelines.

  2. If you installed it — respond

    ppt-creator 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 ppt-creator 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 ppt-creator 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. ppt-creator on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007386

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks ppt-creator-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.