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

jobber-app-template-reactnpm

jobber-app-template-react is a confirmed malicious npm package (MAL-2026-11137) that steals credentials and exfiltrates sensitive data (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in jobber-app-template-react (npm)

MAL-2026-11137
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall jobber-app-template-react

What this malware does

The package's preinstall hook runs index.js which fires automatically on npm install. The script collects host reconnaissance (os.hostname(), os.userInfo().username, home directory, DNS servers, __dirname) and reads the contents of /etc/passwd and /etc/hosts from the installer's machine, then HTTPS-POSTs a JSON payload to the hardcoded Burp Collaborator subdomain 5tzh3l2e1cetr1chf6osh4tg57b0zqnf.oastify.com. The behavior is unrelated to the package's advertised purpose as a React app template and is characteristic of a dependency-confusion exfiltration payload.

Malicious versions

1 flagged
1.0.1

Indicators of compromise (SHA-256)

844a2ac73b588b6c0c7c370dd647685768992ff3e6b5ef492e6fc6dc6be240ce

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

  2. If you installed it — respond

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

Campaign

IN-MAL-2026-010888

References

Credits

  • Amazon Inspector · finder

Detect & block this

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

Explore