Which versions of techportal are malicious?

The following npm versions of techportal are flagged malicious: 4.0.10, 4.0.11. Treat any of these as compromised.

How do I remediate techportal if I installed it?

techportal 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.

I already installed techportal — how do I know if it already compromised me?

If techportal 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.

Is techportal part of a known attack campaign?

Yes — techportal is associated with the IN-MAL-2026-019138, IN-MAL-2026-019482 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find techportal across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for techportal (2 malicious versions).

Malicious package

techportalnpm

Advisory published Aug 29, 2026Updated Sep 4, 2026

techportal is a confirmed malicious npm package (MAL-2026-15561) that steals credentials and exfiltrates sensitive data (malicious versions 4.0.10, 4.0.11). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in techportal (npm)

MAL-2026-15561

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall techportal

What this malware does

package.json declares a preinstall hook (node beacon.js) that fires automatically on npm install. beacon.js reads os.hostname(), os.userInfo().username, and process.cwd(), base32-encodes them, and issues an HTTP GET to a hardcoded bare-IP callback URL http://45.76.249.245/beacon/<token>/techportal/4.0.10, carrying the values in X-Bug-Bounty-Host, X-Bug-Bounty-User, and X-Bug-Bounty-Path headers. If the HTTP beacon fails or times out, the same identifiers are packed as base32-encoded DNS subdomain labels and queried (resolve4/resolve6/resolveTxt) against three hardcoded *.oob.asm5.net collector domains, providing a DNS-tunneling channel that bypasses HTTP egress controls. Destination is not caller-configurable and there is no install-time opt-in. Self-labeling of the beacon as an authorized bug bounty or dual-use tool does not change the data flow: installer host identity leaves the installer's machine on npm install to hardcoded attacker-operated infrastructure.

Malicious versions

2 flagged

4.0.104.0.11

Indicators of compromise (SHA-256)

2d947d5b4ddaa0ea6a25488fb5b5a66b3afc5c8f56d5ac38fb2e95e4b23242f3

f3f611a34296fd636d0200171477f6b85e941d8a99464390df73c7680886c40c

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for techportal (2 malicious versions).
If you installed it — respond
techportal 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.
Did it already run?
If techportal 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. techportal on npm has been identified as a malicious package (versions 4.0.10, 4.0.11 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-019138IN-MAL-2026-019482

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks techportal-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