🚨 Singh Technologies — Job Scam / Hiring Fraud Alert

⚠️ Community Warning: This repository documents reported recruitment experiences, suspicious hiring practices, and supporting evidence associated with the name Singh Technologies and the domain thesinghtechnologies.com.

This repository is intended to help software developers, PHP/Laravel developers, Node.js developers, MERN stack developers, Full Stack Developers, and other IT professionals identify potential recruitment red flags before sharing source code, completing unpaid production work, or providing sensitive personal information.

⚠️ Important Warning

If you are contacted by someone claiming to represent Singh Technologies through Indeed, LinkedIn, WhatsApp, email, or similar platforms, verify the company and recruitment process independently before proceeding.

🚨 DO NOT:

❌ Send complete project source code as a ZIP file to an unknown recruiter.
❌ Complete large unpaid assignments that appear to be production-ready features.
❌ Pay registration, security, training, onboarding, or equipment fees.
❌ Share Aadhaar, PAN, bank details, OTPs, passwords, or other sensitive information.
❌ Install unknown software or give remote access to your computer.
❌ Continue working when salary/payment terms are unclear.
❌ Trust an offer letter merely because it contains company branding.
❌ Share private API keys, cloud credentials, database passwords, or .env files.

🔍 Reported Recruitment Pattern

Based on the experiences documented in this repository, the reported recruitment pattern includes:

Job Platform
↓
Initial Shortlisting
↓
WhatsApp / Email Communication
↓
Interview / Assignment
↓
Large Development Task
↓
Request for Source Code / ZIP
↓
Candidate Continues Working
↓
Payment / Employment Issues Reported

The exact process may differ between candidates. This repository documents reported experiences and available evidence rather than claiming that every interaction follows the same pattern.

🎯 Reported Target Roles

The reported opportunities have included software development positions such as:

PHP Developer
Laravel Developer
Senior Laravel Developer
Node.js Developer
MERN Stack Developer
Backend Developer
Full Stack Developer
Web Developer
Software Developer
API Developer

🌐 Reported Communication Channels

Candidates have reported communication through platforms such as:

Indeed
LinkedIn
WhatsApp
Email
Phone calls

Reported email/domain information should always be independently verified.

🚩 Major Red Flags

1. Large "Assignment" Instead of a Normal Technical Interview

One of the major concerns documented by candidates is receiving a development assignment that appears substantially larger than a normal interview exercise.

A legitimate technical assessment may involve:

A small coding problem
A limited feature
A short system-design exercise
A coding discussion
Pair programming
A short take-home assignment

Candidates should be cautious when an "assignment" requires:

Multiple database tables
Authentication
Admin panels
Complete APIs
Payment/subscription logic
Production-ready UI
Multiple days of development
Repeated bug fixes after submission
Deployment to a real server
Complete source-code delivery

🍱 Reported "Choice Tiffin Services" Assignment

Candidates have reported being asked to develop functionality related to:

https://choicetiffinservices.com

The concern documented here is that the assignment appears to involve substantial development work rather than a limited technical evaluation.

Questions Candidates Should Ask

Before completing such a task, ask:

Is this an internal test project?
Is this code going to production?
Who owns the resulting source code?
Will the candidate be paid for production work?
Can the work be completed inside the company's GitHub organization?
Can the company provide a written scope and evaluation criteria?
Will the candidate receive a written agreement regarding ownership?
Why is a complete production-like application required for an interview?
Who is the actual client for this project?
Is there a contract covering the submitted source code?

If the company refuses to answer these questions, consider withdrawing from the process.

💻 Never Send Your Entire Source Code ZIP

A particularly important lesson from the documented experiences is:

Do not send a complete production-ready project as a ZIP file to an unknown recruiter or company representative.

A safer technical interview workflow is:

Company GitHub Organization
↓
Candidate Repository / Fork
↓
Feature Branch
↓
Pull Request
↓
Code Review
↓
Interview Discussion

This provides:

Commit history
Code ownership clarity
Review history
Timestamped contributions
Better security
Easier rollback
Transparent collaboration

🚨 If Someone Insists on a ZIP File

Ask:

"Can I submit the assignment through your official GitHub organization instead?"

If they refuse, ask:

"Can you provide a written confirmation that this assignment will only be used for evaluation and will not be deployed, sold, transferred, or used for commercial purposes?"

Keep their response as evidence.

🏢 Company Verification Checklist

Before accepting a remote development job, verify:

Corporate Identity

Recruitment Process

Recruiter identity verified
Technical interview conducted
Hiring manager identified
Job description matches actual work
Assignment has reasonable scope
Written employment terms provided
Salary and payment terms clearly documented
Notice period documented
Probation terms documented

Technical Assignment

Assignment is reasonably sized
No production credentials requested
No customer data requested
No complete commercial application requested
Source-code ownership is clearly defined
Deployment requirements are reasonable
Assignment deadline is reasonable
Purpose of the assignment is clearly explained

🔐 Protect Your Personal Information

Never casually send the following to an unverified recruiter:

Aadhaar Card
PAN Card
Passport
Bank account information
Cancelled cheque
OTP
UPI PIN
Passwords
Credit/debit card information
Remote desktop credentials
Personal API keys
AWS credentials
Google Cloud credentials
Database passwords
.env files containing secrets

If KYC documentation is legitimately required after verification, use an appropriate secure company process rather than sending sensitive documents to an unknown WhatsApp number.

🧪 Technical Security Checklist for Developers

Before running code received from an unknown organization, review the project first.

Do NOT blindly execute:

composer install

or

npm install

Review:

composer.json
package.json
composer.lock
package-lock.json
.env.example
Dockerfile
docker-compose.yml
scripts/
Post-install scripts

Look for:

Unknown dependencies
Suspicious install scripts
Credential harvesting
Remote shell commands
Unknown binaries
Obfuscated JavaScript
Unexpected network requests
Cryptocurrency miners
Malicious Composer packages
Malicious NPM packages
Unexpected file downloads
Suspicious cron jobs

Use an isolated environment when testing suspicious code.

📸 Evidence

Evidence should be stored in this repository only after removing sensitive personal information.

Suggested structure:

evidence/

recruitment-message.png
offer-letter-redacted.png
assignment-redacted.png
email-redacted.png
website-screenshot.png
job-posting-redacted.png
timeline.md

Always Redact

Before uploading screenshots or documents, remove:

Phone numbers
Personal email addresses
Aadhaar numbers
PAN numbers
Bank information
OTPs
Passwords
API keys
Personal addresses
Candidate photographs
Private conversations unrelated to the allegation

📝 Candidate Timeline

If you experienced a similar recruitment process, document it objectively.

Example:

Date:
Platform:
Job Title:
Recruiter:
Recruiter Email:
Recruiter Phone:
Interview Process:
Assignment Given:
Assignment Duration:
Requested Deliverable:
Payment Terms:
Communication After Submission:
Evidence:

Avoid exaggeration.

Record exactly what happened and preserve supporting evidence.

📊 Reported Red Flags Summary

Red Flag	Reported
Large development assignment	⚠️
Source-code ZIP requested	⚠️
WhatsApp recruitment communication	⚠️
Unclear employment/payment terms	⚠️
Production-like assignment	⚠️
Company identity requiring verification	⚠️
Company GitHub organization unavailable	⚠️
Large amount of development work before employment	⚠️
Repeated development requests after assignment	⚠️

These entries represent reported concerns and should be independently verified by each reader.

🔎 Reported Company Information

The following information has been associated with the recruitment communications documented by contributors:

Information	Reported Value
Name Used	Singh Technologies
Website	`thesinghtechnologies.com`
Reported Email	`info@thesinghtechnologies.com`
Recruitment Platforms	Indeed / LinkedIn
Communication	WhatsApp / Email / Phone
Reported Technical Roles	Laravel / PHP / Node.js / MERN / Backend / Full Stack

Important: The information above is provided for identification and verification purposes based on reported experiences. Readers should independently verify all information.

🧾 Reported GST / Registration Concerns

Some candidates have reported receiving company documentation containing a GSTIN.

If a company provides a GSTIN, candidates should independently verify it through the appropriate official government portal rather than relying solely on the number printed on an offer letter.

Recommended Verification

Check:

GST registration
Legal business name
Registration status
Registered address
Business type
Applicable jurisdiction

Do not rely solely on screenshots or claims made in recruitment documents.

If verification fails, preserve the official verification result as evidence.

🎭 Reported Attendance / Probation Concerns

Some candidates have reported being provided with an attendance or login portal during the recruitment/employment process.

An attendance portal alone does not prove that an organization is legitimate.

Similarly, statements regarding:

Probation periods
Laptop/equipment after several months
Salary after probation
Future employment confirmation

should be clearly documented in a valid employment agreement.

Candidates should verify the actual legal entity and employment terms independently.

🛡️ What To Do If You Are Currently Involved

If you believe you are experiencing the same recruitment pattern:

1. Stop Unpaid Development Work

Do not continue indefinitely without clear employment and payment terms.

2. Preserve Evidence

Save:

Emails
WhatsApp messages
Job postings
Offer letters
Assignment instructions
Git commits
Screenshots
Payment requests
Website information
Call details where legally appropriate

3. Do Not Delete Evidence

Keep original files privately and create redacted copies for public sharing.

4. Secure Your Accounts

If you already shared credentials:

Change passwords immediately
Revoke API keys
Rotate database credentials
Revoke cloud access
Enable 2FA
Check GitHub activity
Check email login activity
Check server access logs

5. Report Suspicious Activity

Depending on your location and circumstances, consider reporting suspected fraud to the relevant:

Job platform
Payment provider
Cybercrime authority
Government agency
Law-enforcement agency

🚨 If You Already Sent Your Source Code

If you already sent a project ZIP, immediately check whether it contains:

.env
.env.production
AWS credentials
Database passwords
API keys
SMTP credentials
JWT secrets
Private SSH keys
Cloud credentials
Third-party tokens

If yes:

Rotate the credentials immediately.
Change database passwords.
Revoke API keys.
Change SMTP credentials.
Rotate cloud credentials.
Remove exposed secrets from source control.
Check server access logs.
Review GitHub activity.

Never assume that deleting a file from your computer revokes a credential that has already been shared.

🤝 Help Other Developers

If you encountered a similar recruitment experience, you can contribute additional verified and redacted evidence.

Please avoid:

❌ Doxxing individuals
❌ Publishing private information
❌ Publishing passwords/API keys
❌ Threats or harassment
❌ Fake reviews
❌ Manipulated screenshots
❌ Unverified accusations
❌ Publishing unrelated personal conversations

The goal of this repository is:

Developer awareness + evidence preservation + safer recruitment practices.

📢 Share Responsibly

If you believe another developer may be contacted using the same recruitment pattern, share this repository as an informational resource.

Useful places may include:

LinkedIn developer communities
PHP communities
Laravel communities
Node.js communities
MERN communities
Developer Discord/Slack groups
Job-search communities

Always share evidence responsibly and avoid publishing private personal information.

⚖️ Disclaimer

This repository is an informational and community-awareness project.

The information presented here is based on reported experiences and supporting material available to the repository maintainers.

Readers should independently verify claims, corporate registrations, websites, communications, and other information before reaching their own conclusions.

This repository does not represent a court judgment or government determination regarding any individual or organization.

The purpose of this repository is to help developers identify potential recruitment risks and protect themselves from possible exploitation.

🎯 Repository Goals

This project aims to:

🚨 Warn developers about suspicious recruitment patterns
🔐 Protect developers' source code
🛡️ Protect candidates' personal information
📚 Document reported experiences
🔎 Preserve supporting evidence
🤝 Help developers verify companies
💻 Promote safer technical interview practices
🚫 Discourage unpaid production work disguised as technical assignments

⭐ Support the Project

If this repository helped you identify a suspicious recruitment pattern:

⭐ Star the repository
🔗 Share it with other developers
📝 Contribute verified information
📸 Submit redacted evidence
📢 Help spread awareness

One developer's experience can help protect hundreds of other developers.

🔗 Useful Search Keywords

Singh Technologies scam
Singh Technologies job scam
Singh Technologies hiring scam
Singh Technologies fraud
Singh Technologies Laravel job
Singh Technologies PHP job
Singh Technologies Node.js job
Singh Technologies MERN job
Singh Technologies developer job
Singh Technologies unpaid assignment
Singh Technologies unpaid work
Singh Technologies recruitment fraud
thesinghtechnologies.com
Laravel job scam
PHP developer job scam
Node.js job scam
MERN job scam
software developer hiring scam
fake IT company
fake job offer
fake recruitment
unpaid development assignment

📌 Final Message to Developers

A technical interview should evaluate your skills — not obtain a free production application from you.

Before spending days building a "test assignment", ask:

Who is the company?
Who is the client?
Why is this feature required?
Will this code be used commercially?
Who owns the code?
Where will the code be hosted?
Will I be paid for production work?
Can I submit through the company's official GitHub?

If the answers are unclear, stop and verify before continuing.

Maintained as a developer-community awareness and documentation project.

Name		Name	Last commit message	Last commit date
app		app
assets		assets
bootstrap		bootstrap
config		config
database		database
demo		demo
docs		docs
public		public
resources		resources
routes		routes
scratch		scratch
storage/framework		storage/framework
tests		tests
upload		upload
.editorconfig		.editorconfig
.env		.env
.gitattributes		.gitattributes
.gitignore		.gitignore
.htaccess		.htaccess
README.md		README.md
api-endpoints.txt		api-endpoints.txt
artisan		artisan
composer.json		composer.json
composer.lock		composer.lock
composer.phar		composer.phar
db_tifin.sql		db_tifin.sql
dump_db.php		dump_db.php
export.php		export.php
favicon.ico		favicon.ico
index.php		index.php
key.php		key.php
package-lock.json		package-lock.json
package.json		package.json
phpunit.xml		phpunit.xml
qasim-changes.txt		qasim-changes.txt
robots.txt		robots.txt
test_api.php		test_api.php
test_cart.php		test_cart.php
vite.config.js		vite.config.js

Latest commit

History

Folders and files

Repository files navigation