NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

@securihackbot/depconf-flow-1792484611npm

Advisory published Updated

@securihackbot/depconf-flow-1792484611 is a confirmed malicious npm package (MAL-2026-19220) that steals credentials and exfiltrates sensitive data (malicious version 1.2.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @securihackbot/depconf-flow-1792484611 (npm)

MAL-2026-19220
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @securihackbot/depconf-flow-1792484611

What this malware does

Package publishes under the @securihackbot scope as a public dependency-confusion squat of an internal name. The declared postinstall script executes postinstall.js, which on npm install collects host identifiers (os.hostname(), USER/USERNAME, platform, arch, node version, package name, and a nonce), base64-encodes them, and sends them as a query parameter via plain-HTTP GET to a hardcoded bare-IP collector at http://34.143.131.27:18080/. A DNS-exfil fallback resolves NONCE-prefixed subdomains under a configured DNS suffix. The exfiltration fires automatically on install with no opt-in, and any build host whose resolver pulls this public tarball instead of an intended internal @securihackbot/* package will beacon host metadata to the hardcoded collector. The 'authorized research' framing in the README does not gate the behavior, which runs against any installer that resolves this version.

Malicious versions

1 flagged
1.2.1

Indicators of compromise (SHA-256)

6dc8c3628b1d44eca51a5cde6143c1760a5d393b45729f174bab73f76f8641e8

Detection & response playbook

Credential / info stealer

  1. Find it

    Search your lockfiles and build artifacts for @securihackbot/depconf-flow-1792484611 (version 1.2.1).

  2. If you installed it — respond

    @securihackbot/depconf-flow-1792484611 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 @securihackbot/depconf-flow-1792484611 was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @securihackbot/depconf-flow-1792484611 on npm has been identified as a malicious package (version 1.2.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-022762

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @securihackbot/depconf-flow-1792484611-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
@securihackbot/depconf-flow-1792484611 (npm) malicious package — MAL-2026-19220 | O3 Security