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

@intentsolution/database-security-scannernpm

Advisory published Updated

@intentsolution/database-security-scanner is a confirmed malicious npm package (MAL-2026-5825) that opens a backdoor for remote access (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @intentsolution/database-security-scanner (npm)

MAL-2026-5825
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @intentsolution/database-security-scanner

What this malware does

The package's main file (index.js) is heavily obfuscated using obfuscator.io-style string-array rotation, base64 fragments, and per-byte XOR decoders (e.g. H(a0) with key k=[0x70,0xa0,0x89,0x48]) that hide strings such as 'package.json', 'node_modules', '.vscode', 'npm i --silent', 'nohup', 'cd', and 'f.js'. On require(), it collects host identifiers — os.hostname(), os.userInfo().username, os.platform(), Date.now(), process.argv[1] — and beacons them as {ts,type,hid,ss,cc} to a hardcoded C2 endpoint whose host is reassembled at runtime from obfuscated constant arrays (X/z) to evade static detection. The C2 response is used to fetch a second-stage JavaScript payload via GET '<host>/f/<R>', which is written to ~/.vscode/f.js along with a fake package.json; the package then runs cd "<dir>" && npm i --silent and spawns node f.js detached (with nohup on Linux) to persist execution. A setInterval retries the beacon on failure. The package's advertised purpose ("database-security-scanner") is a cover story — package.json has empty author/description/license and no database-scanning code exists; the entire module is the dropper. Any installer that requires this package executes attacker-supplied code fetched at runtime with no hash verification, hidden staging in ~/.vscode, and detached persistence.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged
1.0.0

Indicators of compromise (SHA-256)

7b1f4da3cb40cc2e1396230869d85bcc5a3c9267c0dc3c60dc297c08d1882230
f9da0f58ed03e672c26d8909ef187d2f25944a68e5bc55ead1dde72a15f0ab69

Detection & response playbook

Backdoor / remote access
  1. Find it

    Search your lockfiles and build artifacts for @intentsolution/database-security-scanner (version 1.0.0).

  2. If you installed it — respond

    @intentsolution/database-security-scanner 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 @intentsolution/database-security-scanner 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. @intentsolution/database-security-scanner 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-006703GHSA-gx76-7hhh-jcj2

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @intentsolution/database-security-scanner-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Explore

@intentsolution/database-security-scanner (npm) malicious package — MAL-2026-5825 | O3 Security