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

akrai-reportnpm

Advisory published Updated

akrai-report is a confirmed malicious npm package (MAL-2026-10955) that steals credentials and exfiltrates sensitive data. Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in akrai-report (npm)

MAL-2026-10955
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall akrai-report

What this malware does

The akrai-report package was published to the npm registry by user 'jonothhu' (maintainer email [email protected]) as one of 19 packages in a dependency-confusion campaign targeting the 'markscan', 'akrai', and 'iphouse' namespaces, published in both unscoped and scoped (@scope/name) forms so that a misconfigured resolver installs the public lookalike instead of an intended private/internal dependency. Each package self-describes as an 'AUTHORIZED SECURITY RESEARCH CANARY' (static token PATHC-CANARY-2026, contact [email protected]), but ships an unconsented install-time beacon and provides no legitimate functionality.

The package declares a postinstall hook ("node postinstall.js") that executes automatically on npm install. The bundled postinstall.js collects host reconnaissance - the package/canary name, the static token 'PATHC-CANARY-2026', an event label, a UTC timestamp, the Node.js version, the current working directory, the platform, and os.hostname() - and exfiltrates it via HTTPS POST to a hardcoded anonymous dead-drop at https://webhook.site/129cb2ee-ba08-4b3c-989c-270dc0030350 (the same collector across all 19 packages). Request errors are swallowed.

The self-attestation of 'authorized security research' present in the package metadata is unverifiable and does not change the disposition: the package performs unconsented telemetry collection and exfiltration at install time to an anonymous collector, matching the behavior of a dependency-confusion reconnaissance beacon. Install-time behavior and the shared collector endpoint were confirmed by static analysis of a sample spanning all three namespaces and both scoped and unscoped variants.

Malicious versions

all versions

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

Detection & response playbook

Credential / info stealer

  1. Find it

    Search your lockfiles and build artifacts for akrai-report (all published versions).

  2. If you installed it — respond

    akrai-report 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 akrai-report 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. akrai-report 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

  • SafeDep · finder

Detect & block this

O3 blocks akrai-report-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
akrai-report (npm) malicious package — MAL-2026-10955 | O3 Security