Which versions of @sectest429/hello-npm-world are malicious?

The following npm versions of @sectest429/hello-npm-world are flagged malicious: 1.0.3. Treat any of these as compromised.

How do I remediate @sectest429/hello-npm-world if I installed it?

@sectest429/hello-npm-world 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 @sectest429/hello-npm-world — how do I know if it already compromised me?

If @sectest429/hello-npm-world 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.

Is @sectest429/hello-npm-world part of a known attack campaign?

Yes — @sectest429/hello-npm-world is associated with the IN-MAL-2026-010297 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 @sectest429/hello-npm-world across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @sectest429/hello-npm-world (version 1.0.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @sectest429/hello-npm-world across your stack and pipelines.

Malicious package

@sectest429/hello-npm-worldnpm

Malicious code in @sectest429/hello-npm-world (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-10478

Immediate action

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

npm uninstall @sectest429/hello-npm-world

What this malware does

The package advertises a single function module.exports = function hello(name) but ships a preinstall.js lifecycle script that runs automatically on npm install and performs reconnaissance unrelated to the advertised functionality. The script collects OS username, hostname, platform/arch, and the full running process list (ps -eo comm= on POSIX, tasklist /fo csv /nh on Windows), and issues an HTTP PUT to the AWS EC2 link-local IMDSv2 token endpoint at 169.254.169.254/latest/api/token followed by a fetch of /latest/meta-data/instance-id. Results are written to ./exfil.log in the installer's working directory. The file's own header comment self-describes as a 'SECURITY DEMO payload' proving that a trojanized package gets code execution at install time. Even though the current version writes locally rather than transmitting, the recon chain (process enumeration + cloud-instance fingerprinting) has no relationship to a hello-world library, runs without consent on every install, and pollutes the consumer's CWD with an artifact.

Malicious versions

1 flagged

1.0.3

Indicators of compromise (SHA-256)

479b9303d76a49dfacb402f0a906e32686b5d276e23f429678150e73e506550d

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @sectest429/hello-npm-world (version 1.0.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @sectest429/hello-npm-world across your stack and pipelines.
If you installed it — respond
@sectest429/hello-npm-world 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 @sectest429/hello-npm-world 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.
How O3 protects you
O3 blocks @sectest429/hello-npm-world 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. @sectest429/hello-npm-world on npm has been identified as a malicious package (version 1.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010297

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @sectest429/hello-npm-world-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